This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: locking problem with mips atomicity
- From: Richard Sandiford <rsandifo at redhat dot com>
- To: Michael Eager <eager at mvista dot com>
- Cc: Phil Edwards <phil at jaj dot com>, gcc <gcc at gcc dot gnu dot org>, libstdc++ at gcc dot gnu dot org, Paul Koning <pkoning at equallogic dot com>
- Date: Thu, 18 Mar 2004 11:04:19 +0000
- Subject: Re: locking problem with mips atomicity
- References: <20040316045706.GA5985@redhat.com> <405726C9.86724574@mvista.com><1079458507.3799.8.camel@dzur.sfbay.redhat.com><40573D8F.DAAB6354@mvista.com> <20040316183443.GB12315@redhat.com><4057833F.37693319@mvista.com> <20040316232242.GA6879@redhat.com><40579942.3B51A8B3@mvista.com><20040317004432.GA24875@disaster.jaj.com><4057A10E.1968551E@mvista.com><20040317005526.GA25735@disaster.jaj.com><4058D42A.EA714F43@mvista.com>
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?
Richard