Re: [PATCH 1/3][AArch64] Strengthen barriers for sync-fetch-op builtins.

2015-05-26 Thread James Greenhalgh
On Thu, May 21, 2015 at 04:57:00PM +0100, Matthew Wahab wrote: > On Aarch64, the __sync builtins are implemented using the __atomic operations > and barriers. This makes the the __sync builtins inconsistent with their > documentation which requires stronger barriers than those for the __atomic > bu

Re: [PATCH 1/3][AArch64] Strengthen barriers for sync-fetch-op builtins.

2015-05-22 Thread Matthew Wahab
On 22/05/15 12:26, Ramana Radhakrishnan wrote: Ok for trunk? I can't approve but do you mind taking care of -march=armv8-a in the arm backend too as that would have the same issues. Will do, Matthew

Re: [PATCH 1/3][AArch64] Strengthen barriers for sync-fetch-op builtins.

2015-05-22 Thread Ramana Radhakrishnan
> > Ok for trunk? I can't approve but do you mind taking care of -march=armv8-a in the arm backend too as that would have the same issues. Ramana > Matthew > > gcc/ > 2015-05-21 Matthew Wahab > > * config/aarch64/aarch64.c (aarch64_emit_post_barrier): New. > (aarch64_split_ato

[PATCH 1/3][AArch64] Strengthen barriers for sync-fetch-op builtins.

2015-05-21 Thread Matthew Wahab
On Aarch64, the __sync builtins are implemented using the __atomic operations and barriers. This makes the the __sync builtins inconsistent with their documentation which requires stronger barriers than those for the __atomic builtins. The difference between __sync and __atomic builtins is that t