Displaying 6 results from an estimated 6 matches for "vex_w".
2012 Nov 08
2
[LLVMdev] X86 Tablegen Description and VEX.W
...n 8 November 2012 11:12, Cameron McInally <cameron.mcinally at nyu.edu> wrote:
> On Wed, Nov 7, 2012 at 10:52 PM, Anitha Boyapati <anitha.boyapati at gmail.com>
> wrote:
> ...
>>
>> For the multiclass "fma4s", why is "mr" not inherited from "VEX_W" and
>> "MemOp4" like those of "rm" or "rr" ?
>
>
> Hey Anitha,
>
> The VEX.W bit is used to denote operand order. In other words, this bit
> allows for a memop to be used as either the second or third source operand
> of an FMA instruct...
2012 Nov 08
0
[LLVMdev] X86 Tablegen Description and VEX.W
On Thu, Nov 8, 2012 at 1:34 AM, Anitha Boyapati
<anitha.boyapati at gmail.com>wrote:
...
>
> I actually have confusion in mapping the role of vex_w during
> instruction selection. For the moment, lets just consider vex_w and
> not memop.
>
> [1]. What does " def rr : FMA4<>, VEX_W" mean? As per tablegen
> description, "rr" now inherits FMA4 and VEX_W. However VEX_W is not a
> class, it is an enumerat...
2012 Nov 08
2
[LLVMdev] X86 Tablegen Description and VEX.W
Hi,
A question from r162999 changes:
http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Target/X86/X86InstrFMA.td?r1=162999&r2=162998&pathrev=162999
For the multiclass "fma4s", why is "mr" not inherited from "VEX_W" and
"MemOp4" like those of "rm" or "rr" ?
multiclass fma4s< >
...
def mr : FMA4<opc, MRMSrcMem, (outs RC:$dst),
(ins RC:$src1, x86memop:$src2, RC:$src3),
!strconcat(OpcodeStr,
"\t{$src3, $src2, $src1, $dst|$dst, $...
2012 Nov 08
0
[LLVMdev] X86 Tablegen Description and VEX.W
On Wed, Nov 7, 2012 at 10:52 PM, Anitha Boyapati
<anitha.boyapati at gmail.com>wrote:
...
> For the multiclass "fma4s", why is "mr" not inherited from "VEX_W" and
> "MemOp4" like those of "rm" or "rr" ?
>
Hey Anitha,
The VEX.W bit is used to denote operand order. In other words, this bit
allows for a memop to be used as either the second or third source operand
of an FMA instruction, offering greater flexibilit...
2018 Mar 28
0
x86 instruction format which takes a single 64-bit immediate
...on requires the REX.W it to be set.
hasLockPrefix - Indicates the instruction should be encoded with a 0xF0 lock prefix.
hasREPPrefix - Indicates the instruction should be encoded with a 0xF3 rep prefix.
OpcEnc - Which encoding scheme this instruction uses. Normal, VEX, EVEX, or XOP.
VEX_WPrefix - Controls the value of the VEX.W bit in the encoder also tells the disassembler which instructions ignore VEX.W.
hasVEX_4V - Does this instruction use VEX.vvvv
hasVEX_L - Should this instruction be encoded with VEX.L=1
ignoresVEX_L - Tells the disassembler that VEX.L shoul...
2018 Mar 28
4
x86 instruction format which takes a single 64-bit immediate
I am attempting to create an instruction which takes a single 64-bit
immediate. This doesn't seem like a thing that would exist already (because
who needs an instruction which just takes an immediate?) How might I
implement this easily? Perhaps I could use a format which encodes a
register, which is then unused?
Thanks for the help.
Gus
-------------- next part --------------
An HTML