From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: ebotcazou@libertysurf.fr
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Status Report (2004-03-09)
Date: Thu, 11 Mar 2004 12:15:00 -0000 [thread overview]
Message-ID: <10403111218.AA28637@vlsi1.ultra.nyu.edu> (raw)
In practice, though, there has been a more liberal use of this /u flag
because putting it on several writes to the same memory location doesn't
seem to cause any problem as long as every write to the said location
carries the /u flag (because the memory writes then conflict).
No, I don't think that's right. I'm pretty sure that there is some
code someplace that will fail if there are two writes to the same /u location
and I thought we added code to prevent any such.
next reply other threads:[~2004-03-11 12:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 12:15 Richard Kenner [this message]
2004-03-11 12:39 ` Eric Botcazou
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 20:08 Richard Kenner
2004-03-19 14:22 Richard Kenner
2004-03-19 6:34 Richard Kenner
2004-03-19 12:18 ` Jakub Jelinek
2004-03-11 12:49 Richard Kenner
2004-03-11 14:09 ` Eric Botcazou
2004-03-09 18:09 Mark Mitchell
2004-03-11 9:45 ` Eric Botcazou
2004-03-11 12:48 ` Jakub Jelinek
2004-03-11 21:11 ` Richard Henderson
2004-03-16 16:53 ` Mark Mitchell
2004-03-16 16:59 ` Paul Koning
2004-03-16 17:11 ` Ian Lance Taylor
2004-03-16 17:24 ` Zack Weinberg
2004-03-16 17:25 ` Paul Koning
2004-03-17 10:56 ` Eric Botcazou
2004-03-17 11:49 ` Eric Botcazou
2004-03-17 15:55 ` Mark Mitchell
2004-03-18 8:25 ` Eric Botcazou
2004-03-18 18:31 ` Eric Botcazou
2004-03-18 19:15 ` Mark Mitchell
2004-03-18 23:36 ` Eric Botcazou
2004-03-18 23:41 ` Jakub Jelinek
2004-03-19 1:23 ` Eric Botcazou
2004-03-19 14:31 ` Eric Botcazou
2004-03-19 19:29 ` Mark Mitchell
2004-03-19 20:04 ` Eric Botcazou
2004-03-19 20:23 ` Mark Mitchell
2004-03-20 19:51 ` Eric Botcazou
[not found] ` <405A3F26.2050100@codesourcery.com>
[not found] ` <200403190155.18981.ebotcazou@libertysurf.fr>
2004-03-19 6:42 ` Mark Mitchell
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=10403111218.AA28637@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=ebotcazou@libertysurf.fr \
--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).