From: Andrew Haley <aph@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: New flag: TREE_THIS_NOTRAP
Date: Fri, 11 Jun 2004 20:44:00 -0000 [thread overview]
Message-ID: <16586.2966.954676.584336@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <20040611193748.GA26068@redhat.com>
Richard Henderson writes:
> On Fri, Jun 11, 2004 at 05:41:31PM +0100, Andrew Haley wrote:
> > case INDIRECT_REF:
> > + {
> > + tree t = TREE_OPERAND (expr, 0);
> > + return (TREE_THIS_NOTRAP (t) == false);
>
> So the NOTRAP bit is on the pointer and not the INDIRECT_REF?
It has to be doesn't it? The trapping in
*exp
is a property of exp, not a property of *. If someone attaches
another INDIRECT_REF to exp, it will not be marked as NOTRAP.
I could mark *both* exp and its INDIRECT_REF as notrap, I
guess.
> This seems likely to get lost during gimplification, unless
> you're taking extra special care...
Andrew.
next prev parent reply other threads:[~2004-06-11 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 14:03 Andrew Haley
2004-06-09 21:45 ` Richard Henderson
2004-06-09 21:46 ` Richard Henderson
2004-06-10 12:45 ` Andrew Haley
2004-06-10 18:06 ` Richard Henderson
2004-06-11 18:18 ` Andrew Haley
2004-06-11 20:37 ` Richard Henderson
2004-06-11 20:44 ` Andrew Haley [this message]
2004-06-11 20:49 ` Richard Henderson
2004-06-14 22:26 ` Jason Merrill
2004-06-16 17:17 ` Andrew Haley
2004-06-16 17:17 ` Andrew Haley
2004-06-16 17:35 ` Frank Ch. Eigler
2004-06-16 17:35 ` Andrew Haley
2004-06-16 18:30 ` Richard Henderson
2004-06-15 2:39 ` Tom Tromey
2004-06-15 11:50 ` Andrew Haley
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=16586.2966.954676.584336@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@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).