This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Use 1U everywhere in elf/elf.h.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Andreas Schwab <schwab at linux-m68k dot org>
- Date: Sat, 07 Mar 2015 13:36:01 -0500
- Subject: Re: [PATCH] Use 1U everywhere in elf/elf.h.
- Authentication-results: sourceware.org; auth=none
- References: <54F9E0CE dot 8070303 at redhat dot com> <20150306180147 dot 7EA492C3B32 at topped-with-meat dot com> <54FA28D8 dot 1080209 at redhat dot com> <20150306222818 dot 643092C3B39 at topped-with-meat dot com>
On 03/06/2015 05:28 PM, Roland McGrath wrote:
>> I would like to write a test case for it, but I can't get anything to
>> trigger the original reported failure by readelf when running with
>> Therefore I can't at present even get a reproducer nor write a regression
>> test, but I know what what we have for SHF_EXCLUDE is wrong.
> A regression test for a reported manifest issue is of course worthwhile.
> But I was talking about a generic test that verifies at compile time what
> the types actually are rather than some particular characteristic of behavior.
I mean I could use C++ and the associated RTTI to do the comparison at
runtime and thus produce a detailed analysis of the types.
Is that what you're thinking too?