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: Problem with operand handling
Date: Sat, 04 Sep 2004 14:48:00 -0000	[thread overview]
Message-ID: <10409041451.AA09485@vlsi1.ultra.nyu.edu> (raw)

When I work around the problem with lcm.c, I then get:

../../xgcc -B../../ -c -g -O2      -W -Wall -gnatpg  g-exctra.adb -o g-exctra.o
+===========================GNAT BUG DETECTED==============================+
| 5.03h (20040831) (x86_64-unknown-linux-gnu) GCC error:                   |
| in var_ann, at tree-flow-inline.h:38                                     |

Upon investigating, I find I don't understand something about tree-ssa-operands.

It looks like add_stmt_operand is supposed to be passed a pointer to the
operand.  But in a number of places in tree-ssa-operands.c, you have

	tree var = referenced_var (i);

	add_stmt_operand (&var, ...);

But this puts a pointer into the stack of that function into the operands
of the statement.  That looks very wrong and seems to be causing my problem.
How is that supposed to work?

             reply	other threads:[~2004-09-04 14:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04 14:48 Richard Kenner [this message]
2004-09-07 12:20 ` Andrew MacLeod
2004-09-07 16:41 ` Andrew Pinski
2004-09-07 12:38 Richard Kenner
2004-09-07 13:02 ` Andrew MacLeod
2004-09-07 13:28 Richard Kenner
2004-09-07 13:47 ` 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 20:32 Richard Kenner
2004-09-07 20:48 ` Andrew MacLeod
2004-09-07 21:35 Richard Kenner
2004-09-07 22:52 ` 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=10409041451.AA09485@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).