This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: sync_lock_test_and_set testcases
- From: Richard Henderson <rth at redhat dot com>
- To: Adrian Straetling <straetling at de dot ibm dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 18 Aug 2005 16:54:30 -0700
- Subject: Re: sync_lock_test_and_set testcases
- References: <20050818175341.GA19121@de.ibm.com>
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~