From: Andrew MacLeod <amacleod@redhat.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Problem with operand handling
Date: Tue, 07 Sep 2004 14:51:00 -0000 [thread overview]
Message-ID: <1094568656.31576.0.camel@pain> (raw)
In-Reply-To: <1094568099.21733.44.camel@localhost.localdomain>
On Tue, 2004-09-07 at 10:41, Diego Novillo wrote:
> On Tue, 2004-09-07 at 10:02, Richard Kenner wrote:
>
> > GNAT.EXCEPTION_TRACES.DECORATOR_WRAPPER (traceback, len)
> > {
> > system__traceback_entries__traceback_entry___XDLU_0__18446744073709551615[1 .. T.2] & decorator_traceback;
> >
> What does this declaration mean? Is decorator_traceback
>
> > decorator_traceback_17 = (system__traceback_entries__traceback_entry___XDLU_0__18446744073709551615[1 .. T.2] &) traceback_16;
> >
> According to this, decorator_traceback is a GIMPLE register. It seems
> to be a pointer of some kind? I can't parse the original declaration.
> You'll have to figure out why we first think that decorator_traceback is
> a gimple reg, and then we think otherwise.
>
> This may help. Put this test in add_may_alias:
>
> if (is_gimple_reg (var) || is_gimple_reg (alias))
> abort ();
>
This should probably be added permanently under ENABLE_CHECKING....
Andrew
next prev parent reply other threads:[~2004-09-07 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 13:59 Richard Kenner
2004-09-07 14:41 ` Diego Novillo
2004-09-07 14:51 ` Andrew MacLeod [this message]
2004-09-07 15:46 ` Nathan Sidwell
2004-09-07 15:55 ` Re: Andrew MacLeod
-- strict thread matches above, loose matches on Subject: below --
2004-09-07 21:35 Problem with operand handling 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: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=1094568656.31576.0.camel@pain \
--to=amacleod@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).