From: Zack Weinberg <zack@codesourcery.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Phil Edwards <phil@codesourcery.com>,
law@redhat.com, Jerry Quinn <jlquinn@optonline.net>,
gcc-patches@gcc.gnu.org
Subject: Re: [patch] Minor improvement to typeclass.h
Date: Thu, 10 Jun 2004 21:26:00 -0000 [thread overview]
Message-ID: <87vfhz9o42.fsf@taltos.codesourcery.com> (raw)
In-Reply-To: <m31xknrzsn.fsf@gromit.moeb> (Andreas Jaeger's message of "Thu, 10 Jun 2004 21:14:16 +0200")
Andreas Jaeger <aj@suse.de> writes:
>> I tried getting rid of this header when I was doing compile-time type
>> reflection/introspection on Gaby's now-dead branch. It turned out that
>> glibc used it for some twisted purpose, even though gcc doesn't.
>
> I just did a grep through the current glibc sources and see no
> references to typeclass.h at all. Especially tgmath.h does not
> include it. It might be that tgmath.h could be written in a better
> way with typeclass...
I was unclear. glibc tgmath.h uses __builtin_classify_type. It
doesn't use typeclass.h (nor could it - gcc doesn't install it);
it has hardwired numeric constants for the builtin's return value.
Y'all might find __builtin_types_compatible_p a useable replacement,
but I can't be sure. (Take a look at gcc/config/rs6000/altivec.h for
example usage.)
zw
prev parent reply other threads:[~2004-06-10 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 20:57 Jerry Quinn
2004-06-06 3:29 ` Zack Weinberg
2004-06-06 3:51 ` Jerry Quinn
2004-06-09 22:35 ` Jeffrey A Law
2004-06-10 19:52 ` Zack Weinberg
2004-06-10 19:54 ` Phil Edwards
2004-06-10 20:04 ` Zack Weinberg
2004-06-10 21:25 ` Joseph S. Myers
2004-06-10 21:42 ` Zack Weinberg
2004-06-10 20:31 ` Jeffrey A Law
2004-06-10 20:52 ` Jakub Jelinek
2004-06-10 21:09 ` Andreas Jaeger
2004-06-10 21:26 ` Zack Weinberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vfhz9o42.fsf@taltos.codesourcery.com \
--to=zack@codesourcery.com \
--cc=aj@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlquinn@optonline.net \
--cc=law@redhat.com \
--cc=phil@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).