> > > > > The ll/sc constructs in the kernel use ".set noat" to inhibit use
> > > > > and proceed to use it themselves. This is fine, except for one
> > > > > constraints on memory operands are "o" and "=o", which means
> > > > > memory references. If I'm not mistaken, the assembler will
> > > > > turn these into uses of $at if the offset is not 0 - at least, it
> > > > > seems to do that here (gcc 2.95.3, binutils 184.108.40.206.2). Just
> > > > > with the compiler and asking for a real memory reference does the
> > > >
> > > > Both "m" and "o" seem to be incorrect here as both are the same for
> > > > "R" seems to be appropriate, OTOH. Still gcc 2.95.3 doesn't handle
> > > > fine for all cases, but it works most of the time and emits a
> > > > otherwise. I can't comment on 3.0.
> Back to quibbling - that's just not true. For one thing, from the info
> Memory reference that can be loaded with one instruction (`m'
> is preferable for `asm' statements)
> For another, using the patch I posted below, I get inconsistent
> constraint errors. I'm not entirely sure why. Is there any reason not
> to use the "m" version? I can't see any case in which it would not
> behave correctly.
There seems to be a bug in many older gcc's, where if you use
"m" or "o", and the effective address requires more than 16 bits
of offset relative to an available base register, store address
calculations override the "noat" setting. Load address calculations
are at least smart enough to use the load destination as the
temporary register. Of the compilers that I was able to test,
"R" constraint worked only on the most recent gcc version.
And with that compiler, "m" also generated correct code.
The "m" constraint also worked on earlier gcc's, but
violated the noat constraint on stores. The compilers where
"m" violated noat were also those where the "R" constraint
was rejected as being inconsistent. None of the compilers tested
generated correct code for "R" but incorrect code for "m".
So it could be argued that "m" constraints will in fact
function with a broader range of compilers, albeit with
the quirk that a "noat" override warning may be produced
in the case of older gcc's.