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 21:35:00 -0000 [thread overview]
Message-ID: <10409072138.AA28326@vlsi1.ultra.nyu.edu> (raw)
I think he was looking for the traceback froim this abort() so we can
see where the real operand is incorrectly being added to the alias
list...
Sorry. This was a small enough test case that I already was able to set
a breakpoint there.
It's from compute_flow_insensitive_aliasing. But I see something
interesting. This is in addressable_vars and TREE_ADDRESSABLE isn't
set. That's wrong, isn't it?
next reply other threads:[~2004-09-07 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 21:35 Richard Kenner [this message]
2004-09-07 22:52 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
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 13:28 Richard Kenner
2004-09-07 13:47 ` 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=10409072138.AA28326@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).