Re: [Nasm-devel] adding AVX2 transactional synchronization extensions

[Cyrill G. <gor...@op...>]

On Tue, Feb 14, 2012 at 02:27:52PM -0800, H. Peter Anvin wrote:
> On 02/14/2012 02:24 PM, Cyrill Gorcunov wrote:
> >>
> >>IIRC MOV never requires LOCK, nor does it accept it.
> >>
> >
> >quoting spec:
> >The XRELEASE prefix hint can only be used with the following instructions:
> >
> >  - The "MOV mem, reg" (Opcode 88H/89H) and "MOV mem, imm" (Opcode C6H/C7H) instructions.
> >    In these cases, the XRELEASE is recognized without the presence of the LOCK
> >    prefix.
> >
> >So I seem to miss something obvious?
> >
> 
> Not really... it's what it says up there... doesn't require a LOCK
> prefix.  Note that only some form of MOV is supported, which is
> another reason this needs to be part of the instruction pattern in
> insns.dat.
> 

OK, I seem to understand. Will post patch once it get done (in a couple
of days I hope).

	Cyrill