Displaying 6 results from an estimated 6 matches for "mo_frameindex".
2011 Mar 03
2
[LLVMdev] MachineOperand type
Hi all,
I have a question about the types of MachineOperand. There are 12
different types of MachineOperand such as MO_Register, MO_Immediate and
so on. Some of the names are self-explanatory such as MO_Register and
MO_Immediate. Some of them are a little confusing such as MO_FrameIndex,
MO_ConstantPoolIndex and so on. For example, what is the different
between MO_ExternalSymbol and MO_GlobalAddress? Are these two types
orthogonal? I found that memset and memcpy are MO_ExternalSymbol and
printf and fprintf and so on are MO_GlobalAddress.
Thanks a lot in advance. Any advice wi...
2009 Mar 01
2
[LLVMdev] Shrink Wrapping - RFC and initial implementation
...lustrated by a simple example in which a single CSR is used
in one branch of a conditional. When the stack frame is laid out, the spill
for this CSR is accounted for in the calculation of stack size as it should
be. The stack slot for the CSR is correctly computed and everything seems
fine when the MO_FrameIndex are replaced. The problem is that since the
spill instruction for the CSR (e.g. pushl %esi) is moved from the entry
block, the push does not happen, and the value of %esp in the entry block is
not what it should be to satisfy the offsets produced by
eliminateFrameIndex().
A similar situation exists...
2009 Mar 02
0
[LLVMdev] Shrink Wrapping - RFC and initial implementation
...e in which a single CSR
> is used in one branch of a conditional. When the stack frame is laid
> out, the spill for this CSR is accounted for in the calculation of
> stack size as it should be. The stack slot for the CSR is correctly
> computed and everything seems fine when the MO_FrameIndex are
> replaced. The problem is that since the spill instruction for the
> CSR (e.g. pushl %esi) is moved from the entry block, the push does
> not happen, and the value of %esp in the entry block is not what it
> should be to satisfy the offsets produced by eliminateFrameIndex()...
2009 Mar 01
0
[LLVMdev] Shrink Wrapping - RFC and initial implementation
On Feb 26, 2009, at 2:02 PM, John Mosby wrote:
> Hello LLVMdev,
>
> I have been working with LLVM for just over a year now, mainly in
> the area of compilation for HDLs like SystemVerilog and SystemC.
> Most of this work dealt with translation to LLVM IR, representing
> concurrent languages with LLVM and using LLVM analyses and transforms
> for compiling onto proprietary
2009 Feb 26
4
[LLVMdev] Shrink Wrapping - RFC and initial implementation
Hello LLVMdev,
I have been working with LLVM for just over a year now, mainly in the area
of compilation for HDLs like SystemVerilog and SystemC.
Most of this work dealt with translation to LLVM IR, representing concurrent
languages with LLVM and using LLVM analyses and transforms
for compiling onto proprietary simulation acceleration hardware. All of this
work used the C back end exclusively,
2020 Feb 18
2
Function Return Legalization
Hi llvm-dev,
>> The CopyFromReg->CopyToReg->CopyFromReg sequence doesn’t have the chains set correctly: the second CopyFromReg’s input chain isn’t connected to the CopyToReg’s output chain. (This appears to be the same problem in both graphs.)
The DAG mentioned was generated by the SelectionDAGBuilder and as much as possible, we only modify the files within our target so I tried