From: anonymous c. <nas...@us...> - 2013-11-29 01:11:28
|
>> > 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. I just spotted the change for {vex2} and {vex3}. (I'm going through mail in chronological order.) But yeah, having both, an assembler directive and a command line option would be useful to cope with large chunks of code. :) |