Displaying 4 results from an estimated 4 matches for "movwg".
Did you mean:
movw
2005 Jul 22
0
[LLVMdev] How to partition registers into different RegisterClass?
...on that may work for you would be to define permutations of
the instructions that explicitly specify what type of operands your
instruction takes (because different instructions need different LLVM
opcodes) but the instructions would print out the same, so in your
example:
MOVgg : General, General
MOVwg : Write-only, General
MOVwr : Write-only, Read-only
Note that if they all have the same "mov $dest, $src" print string, they
will be printed out identically, but you need to separate them anyway.
If you look at the X86 backend, you might find many flavors of MOV
instructions as well, but...
2005 Jul 22
2
[LLVMdev] How to partition registers into different RegisterClass?
Hi, everyone.
I' have three set of registers - read-only regs, general purpose regs
(read and write), and write-only regs. How should I partition them
into different RegisterClasses so that I can easy define the
instruction?
All RegisterClasses must be mutally exclusive. That is, a register can
only be in a RegisterClass. Otherwise TableGen will raise an error
message.
def
2005 Jul 22
2
[LLVMdev] How to partition registers into different RegisterClass?
...o define permutations of
> the instructions that explicitly specify what type of operands your
> instruction takes (because different instructions need different LLVM
> opcodes) but the instructions would print out the same, so in your
> example:
>
> MOVgg : General, General
> MOVwg : Write-only, General
> MOVwr : Write-only, Read-only
>
> Note that if they all have the same "mov $dest, $src" print string, they
> will be printed out identically, but you need to separate them anyway.
> If you look at the X86 backend, you might find many flavors of MOV...
2005 Jul 22
0
[LLVMdev] How to partition registers into different RegisterClass?
...t;> the instructions that explicitly specify what type of operands your
>> instruction takes (because different instructions need different LLVM
>> opcodes) but the instructions would print out the same, so in your
>> example:
>>
>> MOVgg : General, General
>> MOVwg : Write-only, General
>> MOVwr : Write-only, Read-only
>>
>> Note that if they all have the same "mov $dest, $src" print string, they
>> will be printed out identically, but you need to separate them anyway.
>> If you look at the X86 backend, you might find m...