From: Michael Eager <eager@mvista.com>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: Phil Edwards <phil@jaj.com>, gcc <gcc@gcc.gnu.org>,
libstdc++@gcc.gnu.org, Paul Koning <pkoning@equallogic.com>
Subject: Re: locking problem with mips atomicity
Date: Thu, 18 Mar 2004 16:18:00 -0000 [thread overview]
Message-ID: <4059CBA5.FD8D4C73@mvista.com> (raw)
In-Reply-To: <877jxito0c.fsf@redhat.com>
Richard Sandiford wrote:
>
> Michael Eager <eager@mvista.com> writes:
> > I've revised the patch. It now only has constraints which are referenced.
> > I added a "memory" constraint.
>
> Sorry if I've missed the explanation, but why is using a memory clobber
> an improvement over an unused memory operand?
The location which is clobbered is unknown. From what I understand, an
unused memory operand is ignored.
--
Michael Eager eager@mvista.com 408-328-8426
MontaVista Software, Inc. 1237 E. Arques Ave., Sunnyvale, CA 94085
next prev parent reply other threads:[~2004-03-18 16:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 23:57 Michael Eager
2004-03-16 0:13 ` Phil Edwards
2004-03-16 1:08 ` Michael Eager
2004-03-16 3:12 ` Eric Christopher
2004-03-16 4:57 ` Richard Henderson
2004-03-16 16:10 ` Michael Eager
2004-03-16 17:35 ` Eric Christopher
2004-03-16 17:47 ` Michael Eager
2004-03-16 18:34 ` Richard Henderson
2004-03-16 22:46 ` Michael Eager
2004-03-16 22:49 ` Eric Christopher
2004-03-16 23:27 ` Richard Henderson
2004-03-16 23:33 ` Eric Christopher
2004-03-17 0:28 ` Michael Eager
2004-03-17 0:51 ` Phil Edwards
2004-03-17 0:55 ` Michael Eager
2004-03-17 1:19 ` Phil Edwards
2004-03-17 22:45 ` Michael Eager
2004-03-18 12:21 ` Richard Sandiford
2004-03-18 16:18 ` Michael Eager [this message]
2004-03-18 16:25 ` Richard Henderson
2004-03-18 16:35 ` Richard Sandiford
2004-03-17 22:59 ` Michael Eager
2004-03-18 1:02 ` Richard Henderson
2004-03-18 7:49 ` Michael Eager
2004-03-19 8:26 ` Phil Edwards
2004-03-20 2:56 ` Michael Eager
2004-03-20 3:39 ` Phil Edwards
2004-03-17 1:30 ` Richard Henderson
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=4059CBA5.FD8D4C73@mvista.com \
--to=eager@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=phil@jaj.com \
--cc=pkoning@equallogic.com \
--cc=rsandifo@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).