public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: law@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: Question on cfg_remove_useless_stmts_bb
Date: Wed, 18 Aug 2004 11:52:00 -0000	[thread overview]
Message-ID: <10408181142.AA16853@vlsi1.ultra.nyu.edu> (raw)

    the fact that it wasn't obvious to you is a good indication that I
    should have had more comments in that code.

Actually, there's still some confusion there.  Now that you've pointed it
out, from the way I read that code, VAL is always either a PARM_DECL or
a VAR_DECL.  So why test !TREE_CONSTANT (val)?

And why exclude a constant anyway

             reply	other threads:[~2004-08-18 11:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 11:52 Richard Kenner [this message]
2004-09-01  6:22 ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
2004-08-18 11:51 Richard Kenner
2004-08-17 16:49 Richard Kenner
2004-08-18  8:42 ` Jeffrey A Law
2004-08-17 12:31 Richard Kenner
2004-08-17 15:49 ` Jeffrey A Law
2004-08-13 21:29 Richard Kenner
2004-08-13 19:59 Richard Kenner
2004-08-13 20:19 ` Diego Novillo
2004-08-17  8:26 ` Jeffrey A Law

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=10408181142.AA16853@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.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).