This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: locking problem with mips atomicity

From: Eric Christopher <echristo at redhat dot com>
To: Michael Eager <eager at mvista dot com>
Cc: Richard Henderson <rth at redhat dot com>, gcc <gcc at gcc dot gnu dot org>
Date: Tue, 16 Mar 2004 09:35:07 -0800
Subject: Re: locking problem with mips atomicity
References: <405642CE.F6DB290F@mvista.com> <20040316045706.GA5985@redhat.com> <405726C9.86724574@mvista.com>

> > Better is to make the compiler force the address into a register.
> > It may already be that way, resulting in "la r3,0(r4)".
> 
> This is exactly what this code does.   

He means to force it in without using the la macro.

In fact, I think I'd prefer this.

-eric

-- 
Eric Christopher <echristo@redhat.com>

Follow-Ups:
- Re: locking problem with mips atomicity
  - From: Michael Eager

References:
- locking problem with mips atomicity
  - From: Michael Eager
- Re: locking problem with mips atomicity
  - From: Richard Henderson
- Re: locking problem with mips atomicity
  - From: Michael Eager

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]