This is the mail archive of the
mailing list for the GCC project.
Re: glibc broken with 3.4...
- From: Richard Henderson <rth at redhat dot com>
- To: Jan Hubicka <jh at suse dot cz>
- Cc: Jan Hubicka <hubicka at ucw dot cz>, Andreas Jaeger <aj at suse dot de>, gcc at gcc dot gnu dot org, zack at codesourcery dot com, geoffk at apple dot com
- Date: Sun, 7 Sep 2003 14:32:08 -0700
- Subject: Re: glibc broken with 3.4...
- References: <firstname.lastname@example.org> <20030906185819.GA1599@kam.mff.cuni.cz> <email@example.com> <20030907110551.GL1599@kam.mff.cuni.cz> <firstname.lastname@example.org> <20030907124924.GB14387@kam.mff.cuni.cz> <email@example.com> <20030907135829.GD14387@kam.mff.cuni.cz> <20030907191453.GB14325@redhat.com> <20030907203821.GO14387@kam.mff.cuni.cz>
On Sun, Sep 07, 2003 at 10:38:21PM +0200, Jan Hubicka wrote:
> This is what is done in glibc. This would be acceptable, but __typeof
> (__isinf) counts as used so error fires.
Ug. I've no idea what to do about this, except to somehow note that
sizeof, typeof, alignof doesn't actually use the assembler level symbol
at all. That's pretty sketchy though, cause I'm sure that folks will
say the same thinga bout __builtin_constant_p or anything else that
doesn't really depend on some bits of metadata associated with a symbol.
For C++ I'm sure that it still needs to be a "use" of some sort, since
it'll require templates to be instantiated, etc.