Re: [Nasm-devel] [nasm:master] AVX-512: Add {evex} instruction prefix

[Marat D. <ma...@gm...>]

Some time ago I asked about a mechanism for fine-grained selection of
instruction forms, which is similar to what you do with {evex}, {vec2} and
{vec3} keywords.
Here are the details:

http://comments.gmane.org/gmane.comp.lang.nasm.devel/3347
http://forum.nasm.us/index.php?topic=1517


Maybe you could implement selection between other forms (e.g. REX vs
no-REX) as a part of your new selection mechanism?

Regards,
Marat

On Thu, Nov 28, 2013 at 7:54 PM, Song, Jin Kyu <jin...@in...>wrote:

> > > For instructions that can be encoded either in VEX or EVEX,
> > > {evex} forces nasm to encode in EVEX.
> >
> > In addition to a per-instruction selection mechanism
> > you also want a global selection mechanism, i.e. an
> > assembler directive and a command line option. And
> > as a result of that, you then want {vex} as well.
>
> Yes, adding {vex} - actually {vex2} and {vex3} - is on my to-do list. I
> will implement that as soon as possible. A global selection mechanism is
> now added to my to-do list.
>
> Thanks,
> Jin
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> _______________________________________________
> Nasm-devel mailing list
> Nas...@li...
> https://lists.sourceforge.net/lists/listinfo/nasm-devel
>