Displaying 3 results from an estimated 3 matches for "addressy".
Did you mean:
address
2006 Jun 27
0
[LLVMdev] Mapping bytecode to X86
...a := b
> a := a op c a := c
Yes.
> 2) a := a op c --> a := c
Yes
> 3) a := b op a --> a := a op b --> a := b (???)
No.
> What if the operation in (3) is non-commutative?
2-address instructions are only two-addressy in their first two operands.
You can't join the first and third operand.
Note that the 2-addr pass does all of the above for you, but it does
destroy SSA.
-Chris
> Thanks a lot,
>
> Fernando
>
>> On Mon, 26 Jun 2006, Fernando Magno Quintao Pereira wrote:
>>> The...
2004 Dec 03
2
[LLVMdev] Adding xadd instruction to X86
Chris Lattner wrote:
> On Thu, 2 Dec 2004, Brent Monroe wrote:
>
>>I'm trying to add the xadd instruction to the X86 back end.
>>xadd r/m32, r32
>>exchanges r/m32 and r32, and loads the sum into r/m32. I'm
>>interested in the case where the destination operand is a
>>memory location.
>>
>>I've added the following entry to
2006 Jun 27
2
[LLVMdev] Mapping bytecode to X86
Thank you Chris. I will try to implement the TwoAddress pass to run on
machine code. Why it has not been originally implemented to run on
machine code? Is there anything that makes it troublesome after RA
has been performed? Could you tell me if the transformations below
are correct?
1) a := b op c --> a := b --> a := b
a := a op c a