public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mrs@windriver.com
Cc: gcc@gcc.gnu.org
Subject: Re: new __builtin_choose_type (patch) (new builtin_equal_types patch)
Date: Thu, 04 Oct 2001 19:19:00 -0000	[thread overview]
Message-ID: <10110050225.AA27398@vlsi1.ultra.nyu.edu> (raw)

    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.

             reply	other threads:[~2001-10-04 19:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 19:19 Richard Kenner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-07 19:36 new __builtin_choose_type (patch) (new builtin_equal_typespatch) Aldy Hernandez
2001-10-08  3:46 ` new __builtin_choose_type (patch) (new builtin_equal_types patch) Joseph S. Myers
2001-10-05 11:47 mike stump
2001-10-05 11:52 ` Joseph S. Myers
2001-10-04 19:33 mike stump
2001-10-05  3:01 ` Jakub Jelinek
2001-10-05  4:02   ` Joseph S. Myers
2001-10-05 16:14     ` Richard Henderson
2001-10-05 16:38       ` Joseph S. Myers
2001-10-05 16:57         ` Richard Henderson
2001-10-07 16:56     ` Aldy Hernandez
2001-10-07 17:06       ` Joseph S. Myers
2001-10-04 19:09 mike stump
2001-10-03  1:15 new __builtin_choose_type (patch) Magnus Fromreide
2001-10-03 20:16 ` new __builtin_choose_type (patch) (new builtin_equal_typespatch) Aldy Hernandez
2001-10-03 20:33   ` new __builtin_choose_type (patch) (new builtin_equal_types patch) Stan Shebs
2001-10-03 20:53   ` Daniel Jacobowitz
2001-10-04  6:02     ` Joseph S. Myers
2001-10-05 16:04   ` Richard Henderson

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=10110050225.AA27398@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@windriver.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).