`asm' in natObject.cc

Mon Dec 3 05:38:00 GMT 2001

Boehm, Hans writes:
 > > From: Bryce McKinlay
 > 
 > > I'm guessing that its a libgcj bug, but a g++ bug that it doesn't get 
 > > reported at -O2. I'm no "asm" expert, but this fixed it for me:
 > 
 > The "0" constraint specifies that the input argument must be in the same
 > location as the zeroth output operand. This is very similar to one of the
 > examples in the gcc manual. (See
 > http://gcc.gnu.org/onlinedocs/gcc_6.html#SEC117.) This seems more accurate
 > to me than the patched version. The manual suggests that it would also be
 > OK to use "+m" instead of "=m" as the constraint for the 0th operand, and
 > then delete the second mention of (*addr)). If we need a workaround, I
 > think that would be preferable.
That's better, I think.
 > So far, I'm not convinced that there is anything wrong with natObject.cc.
Neither am I.
What is the memory clobber for?
Andrew.