Displaying 3 results from an estimated 3 matches for "acc58195".
2010 Jun 09
0
[LLVMdev] Always unfold memory operand
On Tue, Jun 8, 2010 at 4:20 PM, David Meyer <pdox at google.com> wrote:
> Hi Eli,
> I have tried this, but the resulting tool-chain was broken.
> There are only two references to "CALL64m": the definition in
> X86Instr64bit.td, and an entry in X86InstrInfo.cpp.
> After commenting both out, compilation of a large application fails with:
> llc: ScheduleDAG.cpp:462:
2010 Jun 09
1
[LLVMdev] Always unfold memory operand
...4m instruction, or
> >> make it require a target feature your target doesn't have.
> >>
> >> -Eli
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100608/acc58195/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BeforeISEL.pdf
Type: application/pdf
Size: 6163 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100608/acc58195/attachment.pdf>
-------------- next pa...
2010 Jun 08
2
[LLVMdev] Always unfold memory operand
Hi Eli,
I have tried this, but the resulting tool-chain was broken.
There are only two references to "CALL64m": the definition in
X86Instr64bit.td, and an entry in X86InstrInfo.cpp.
After commenting both out, compilation of a large application fails with:
llc: ScheduleDAG.cpp:462: void
llvm::ScheduleDAGTopologicalSort::InitDAGTopologicalSorting(): Assertion
`Node2Index[SU->NodeNum]