This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Document __ATOMIC_HLE_ACQUIRE/RELEASE
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Andi Kleen <andi at firstfloor dot org>
- Cc: gcc-patches at gcc dot gnu dot org, Andi Kleen <ak at linux dot intel dot com>
- Date: Fri, 9 Nov 2012 16:19:34 +0100
- Subject: Re: [PATCH] Document __ATOMIC_HLE_ACQUIRE/RELEASE
- References: <1352473455-12009-1-git-send-email-andi@firstfloor.org>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Nov 09, 2012 at 04:04:15PM +0100, Andi Kleen wrote:
> +Additional target specific flags that can be ored with the memory models.
> +@table @code
> +@item __ATOMIC_HLE_ACQUIRE
> +(on i386/x86_64). Start a Hardware Lock Elision transaction with the atomic
> +operation. The memory model must be @code{__ATOMIC_ACQUIRE} or stronger.
Two spaces after . instead of just one.
> +@item __ATOMIC_HLE_RELEASE
> +(on i386/x86_64). Commit a Hardware Lock Elision transaction with the atomic
> +operation. The memory model must be @code{__ATOMIC_RELEASE} or stronger.
> +@end table
> +
> When implementing patterns for these built-in functions, the memory model
> parameter can be ignored as long as the pattern implements the most
> restrictive @code{__ATOMIC_SEQ_CST} model. Any of the other memory models
Jakub