From: "Dave Korn" <dave.korn@artimi.com>
To: "'Robert Dewar'" <dewar@gnat.com>,
"'Richard Kenner'" <kenner@vlsi1.ultra.nyu.edu>
Cc: <dewar@adacore.com>, <gcc@gcc.gnu.org>
Subject: RE: Why doesn't combine like volatiles? (volatile_ok again, sorry!)
Date: Tue, 22 Nov 2005 19:02:00 -0000 [thread overview]
Message-ID: <SERRANOmmlQ080Gxw8Z00000099@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <438365B0.3070406@gnat.com>
Robert Dewar wrote:
> Richard Kenner wrote:
>
>> The issue is that we currently don't combine if volatile is anywhere in
>> sight, whether or not we'd be affecting that access. Just because you
>> have something volatile on the LHS doesn't mean we can't combine into
>> the RHS. A good example are addressing modes: if we have a MEM->MEM
>> copy with one side volatile, doing anything inside the addressing
>> computation of either (even the volatile one) is perfectly safe.
>
> OK, in that case you have to add to the list of restrictions that you
> never combine volatile references.
It's because of the complexity of thinking through all these issues that my
first suggestion was so conservative.
>I did not see that in the list.
Isn't it pretty much implied by point 1, "Not more than one volatile memory
ref appears in the instructions being considered"?
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2005-11-22 19:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 16:16 Richard Kenner
2005-11-22 18:38 ` Robert Dewar
2005-11-22 19:02 ` Dave Korn [this message]
2005-11-22 19:10 ` Robert Dewar
2005-11-22 20:39 ` Dave Korn
2005-11-23 11:27 ` Richard Earnshaw
2005-11-23 11:41 ` Robert Dewar
2005-11-23 12:04 ` Richard Earnshaw
2005-11-23 12:15 ` Robert Dewar
-- strict thread matches above, loose matches on Subject: below --
2005-11-28 18:50 Richard Kenner
2005-11-28 20:25 ` Mike Stump
2005-11-28 20:40 ` Andrew Pinski
2005-11-28 21:55 ` Mike Stump
2005-11-28 22:14 ` Andrew Pinski
2005-11-28 17:28 Richard Kenner
2005-11-28 17:44 ` Mike Stump
2005-11-21 18:12 Dave Korn
2005-11-21 21:46 ` Ian Lance Taylor
2005-11-22 10:45 ` Richard Earnshaw
2005-11-22 15:33 ` Dave Korn
2005-11-22 15:52 ` Richard Earnshaw
2005-11-22 16:10 ` Robert Dewar
2005-11-27 3:18 ` Mike Stump
2005-11-27 3:14 ` Mike Stump
2005-11-28 11:01 ` Richard Earnshaw
2005-11-28 11:13 ` Robert Dewar
2005-11-28 13:09 ` Paolo Bonzini
2005-11-28 21:05 ` Laurent GUERBY
2005-11-28 22:26 ` Robert Dewar
2005-11-28 17:14 ` Mike Stump
2005-11-28 17:19 ` Andrew Pinski
2005-11-28 17:22 ` Mike Stump
2005-11-28 17:35 ` Mike Stump
2005-11-28 17:41 ` Andrew Pinski
2005-11-28 17:53 ` Mike Stump
2005-11-28 18:08 ` Joe Buck
2005-11-28 18:28 ` Mike Stump
2005-11-28 19:12 ` Robert Dewar
2005-11-28 19:56 ` Mike Stump
2005-11-28 20:01 ` Robert Dewar
2005-11-28 20:18 ` Gabriel Dos Reis
2005-11-28 20:21 ` Robert Dewar
2005-11-28 19:05 ` Robert Dewar
2005-11-28 19:53 ` Mike Stump
2005-11-28 17:11 ` Mike Stump
2005-11-28 17:29 ` Dave Korn
2005-11-28 18:14 ` Mike Stump
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=SERRANOmmlQ080Gxw8Z00000099@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=dewar@adacore.com \
--cc=dewar@gnat.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).