public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: amacleod@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: Problem with operand handling
Date: Tue, 07 Sep 2004 13:28:00 -0000	[thread overview]
Message-ID: <10409071331.AA24912@vlsi1.ultra.nyu.edu> (raw)

    > It was happening via a TMT "variable".

    These are alias variables and should never pass the is_gimple_test, so
    we ought not be doing anything with the address being passed into
    add_stmt_operand, the entire function should be dealing with just the
    'var' aspect of whats being passed in.

    Does your variable pass this causing it to be a gimple_reg?  Perhaps a
    flag is set incorrectly or something?

OK, I went back to the code before any of my changes.

The add_stmt_operand is being called from the EXECUTE_IF_SET_IN_BITMAP
call that's looking at call_clobbered_vars.  The variable in this case is
decorator_traceback and is_gimple_reg is set.  In the initial case,
a TMT variable isn't involved.

             reply	other threads:[~2004-09-07 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 13:28 Richard Kenner [this message]
2004-09-07 13:47 ` Andrew MacLeod
  -- strict thread matches above, loose matches on Subject: below --
2004-09-07 21:35 Richard Kenner
2004-09-07 22:52 ` Richard Henderson
2004-09-07 20:32 Richard Kenner
2004-09-07 20:48 ` Andrew MacLeod
2004-09-07 13:59 Richard Kenner
2004-09-07 14:41 ` Diego Novillo
2004-09-07 14:51   ` Andrew MacLeod
2004-09-07 12:38 Richard Kenner
2004-09-07 13:02 ` Andrew MacLeod
2004-09-04 14:48 Richard Kenner
2004-09-07 12:20 ` Andrew MacLeod
2004-09-07 16:41 ` Andrew Pinski

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=10409071331.AA24912@vlsi1.ultra.nyu.edu \
    --to=kenner@vlsi1.ultra.nyu.edu \
    --cc=amacleod@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /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).