From: Jeff Law <law@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: Aldy Hernandez <aldyh@redhat.com>,
Ian Lance Taylor <iant@google.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Guenther <richard.guenther@gmail.com>,
Ian Lance Taylor <ian@airs.com>,
Jakub Jelinek <jakub@redhat.com>,
Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [path] PR 54900: store data race in if-conversion pass
Date: Wed, 17 Oct 2012 05:18:00 -0000 [thread overview]
Message-ID: <507E2424.7070707@redhat.com> (raw)
In-Reply-To: <507E0F25.8010605@redhat.com>
On 10/16/2012 07:51 PM, Richard Henderson wrote:
> On 2012-10-17 09:53, Aldy Hernandez wrote:
>> +/* Like memory_modified_in_insn_p, but return TRUE if INSN will
>> + *SURELY* modify the memory contents of MEM. */
>> +bool
>> +memory_surely_modified_in_insn_p (const_rtx mem, const_rtx insn)
>
> I don't like the word "surely". Are we certain or not?
>
> It's longer, but perhaps "definitely" or "must_be"?
I'd go with "must_be" or something similar. "must" is pretty common
terminology when talking about aliasing properties.
jeff
next prev parent reply other threads:[~2012-10-17 3:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 12:53 Aldy Hernandez
2012-10-15 14:25 ` Andrew MacLeod
2012-10-16 17:32 ` Ian Lance Taylor
2012-10-16 17:33 ` Jakub Jelinek
2012-10-17 0:33 ` Aldy Hernandez
2012-10-17 0:54 ` Ian Lance Taylor
2012-10-19 1:41 ` Aldy Hernandez
2012-10-17 0:26 ` Aldy Hernandez
2012-10-17 0:54 ` Ian Lance Taylor
2012-10-17 4:54 ` Richard Henderson
2012-10-17 5:18 ` Jeff Law [this message]
2012-10-17 21:48 ` Aldy Hernandez
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=507E2424.7070707@redhat.com \
--to=law@redhat.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=iant@google.com \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
--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).