sync_lock_test_and_set testcases
Richard Henderson
rth@redhat.com
Fri Aug 19 00:03:00 GMT 2005
On Thu, Aug 18, 2005 at 07:53:41PM +0200, Adrian Straetling wrote:
> However, in md.texi it states: "The true contents of the memory operand
> are implementation defined." Does this testcase intentionally check for
> compare_exchange behaviour or is it overly stringent?
>
> A fix could be to mask the result with 1 before comparing? At least that
> would work for me.
I suppose you could change the test to != 0. I don't see supporting
the pa test-and-clear variant with this.
r~
More information about the Gcc-patches
mailing list