[LLVMdev] Making Sense of ISel DAG Output
David Greene
dag at cray.com
Fri Oct 3 13:46:25 PDT 2008
On Thursday 02 October 2008 16:19, David Greene wrote:
> %reg1059<def> = MOVSX64rm32 %reg1033, 1, %reg0, 4, Mem:LD(4,4) [tmp163 +
> 0] ; srcLine 10
> %reg1060<def> = MOVSDrm %reg1026, 8, %reg1059, 4294967288, Mem:LD(8,8)
> [r45154 + 0] ; srcLine 10
> %reg1061<def> = MOVSX64rm32 %reg1033, 1, %reg0, 0, Mem:LD(4,4) [iv.161162
> + 0] ; srcLine 10
> %reg1062<def> = MOVSDrm %reg1026, 8, %reg1061, 4294967288, Mem:LD(8,8)
> [r30158 + 0] ; srcLine 10
> %reg1063<def> = MOVSD2PDrm %reg1026, 8, %reg1059, 4294967288, Mem:LD(8,8)
> [r30158 + 0]LD(8,8) [r45154 + 0] ; srcLine 10
> %reg1064<def> = MOVSD2PDrm %reg1026, 8, %reg1059, 4294967288, Mem:LD(8,8)
> [r30158 + 0]LD(8,8) [r45154 + 0] ; srcLine 10
> %reg1065<def> = SHUFPDrri %reg1063, %reg1064, 0 ; srcLine 10
>
> Where the <bleep> are these extra dead MOVSDrms coming from? Note that the
> extra MOVSDrms at least seem to use the correct addresses.
Ok, I figured out why I'm not getting the correct addresses for the
MOVSD2PDrms. It's another tblgen bug I have to patch. So I'll fix that and
see what happens.
-Dave
More information about the llvm-dev
mailing list