On 09/11/2015 05:15 PM, John David Anglin wrote:
On 2015-09-11 4:15 AM, Bernd Schmidt wrote:
On 09/11/2015 01:21 AM, John David Anglin wrote:
As noted in the PR, expand_atomic_compare_and_swap can generate wrong
code when libcalls are emitted
for the sync_compare_and_swap and the result compari
On 2015-09-11 4:15 AM, Bernd Schmidt wrote:
On 09/11/2015 01:21 AM, John David Anglin wrote:
As noted in the PR, expand_atomic_compare_and_swap can generate wrong
code when libcalls are emitted
for the sync_compare_and_swap and the result comparison test. This is
fixed by emitting a move insn t
On 09/11/2015 01:21 AM, John David Anglin wrote:
As noted in the PR, expand_atomic_compare_and_swap can generate wrong code when
libcalls are emitted
for the sync_compare_and_swap and the result comparison test. This is fixed by
emitting a move insn to copy
the result rtx of the sync_compare_a
As noted in the PR, expand_atomic_compare_and_swap can generate wrong code when
libcalls are emitted
for the sync_compare_and_swap and the result comparison test. This is fixed by
emitting a move insn to copy
the result rtx of the sync_compare_and_swap libcall to target_oval instead of
directly
