This is the mail archive of the
mailing list for the GCC project.
Re: new __builtin_choose_type (patch) (new builtin_equal_types patch)
- To: kenner at vlsi1 dot ultra dot nyu dot edu
- Subject: Re: new __builtin_choose_type (patch) (new builtin_equal_types patch)
- From: mike stump <mrs at windriver dot com>
- Date: Thu, 4 Oct 2001 19:33:13 -0700 (PDT)
- Cc: gcc at gcc dot gnu dot org
> Date: Thu, 4 Oct 01 22:25:34 EDT
> From: firstname.lastname@example.org (Richard Kenner)
> To: email@example.com
> Cc: firstname.lastname@example.org
> In a frontend, we never play with modes... The type can be found in
> TREE_TYPE, and you should just use it. This is frontend code.
> Mostly, but not totally, true. When stripping NOPs to look for
> things, it's not uncommon for frontends to only strip NOPs that
> don't change the mode.
Sure, but you're going into way too much detail here. I'd just add,
just in case people don't see the difference, bool != int, from a type
system perspective, it doesn't matter if they both are 32 bits.
Comparing modes can have them be the same. Comparing types, they
never are, well, cept maybe in C when you use a typedef.