search for: addiurxpcimmx16

Displaying 7 results from an estimated 7 matches for "addiurxpcimmx16".

2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...s are that you need to preserve. >> >> —Owen > I have two machine instructions that I need to be together. > > BuildMI(MBB, I, DL, TII.get(Mips::LiRxImmAlignX16), V0) > .addExternalSymbol("_gp_disp", MipsII::MO_ABS_HI); > BuildMI(MBB, I, DL, TII.get(Mips::AddiuRxPcImmX16), V1) > .addExternalSymbol("_gp_disp", MipsII::MO_ABS_LO); > > It's in Mips16ISelDagToDag.cpp > > these two have to be together because they are both part of a complex pc relative calculation. > > I have not used bundles yet and was just looking for an easy...
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...> -Owen > >> I have two machine instructions that I need to be together. > >> > >> BuildMI(MBB, I, DL, TII.get(Mips::LiRxImmAlignX16), V0) > >> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_HI); > >> BuildMI(MBB, I, DL, TII.get(Mips::AddiuRxPcImmX16), V1) > >> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_LO); > >> > >> It's in Mips16ISelDagToDag.cpp > >> > >> these two have to be together because they are both part of a complex pc > relative calculation. > >> > >...
2013 Sep 17
0
[LLVMdev] forcing two instructions to be together
...ve. >>> >>> —Owen >> I have two machine instructions that I need to be together. >> >> BuildMI(MBB, I, DL, TII.get(Mips::LiRxImmAlignX16), V0) >> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_HI); >> BuildMI(MBB, I, DL, TII.get(Mips::AddiuRxPcImmX16), V1) >> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_LO); >> >> It's in Mips16ISelDagToDag.cpp >> >> these two have to be together because they are both part of a complex pc relative calculation. >> >> I have not used bundles yet and was...
2013 Sep 18
2
[LLVMdev] forcing two instructions to be together
...;>> I have two machine instructions that I need to be together. >>>> >>>> BuildMI(MBB, I, DL, TII.get(Mips::LiRxImmAlignX16), V0) >>>> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_HI); >>>> BuildMI(MBB, I, DL, TII.get(Mips::AddiuRxPcImmX16), V1) >>>> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_LO); >>>> >>>> It's in Mips16ISelDagToDag.cpp >>>> >>>> these two have to be together because they are both part of a complex pc >> relative calculation. &gt...
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...;>> I have two machine instructions that I need to be together. >>>> >>>> BuildMI(MBB, I, DL, TII.get(Mips::LiRxImmAlignX16), V0) >>>> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_HI); >>>> BuildMI(MBB, I, DL, TII.get(Mips::AddiuRxPcImmX16), V1) >>>> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_LO); >>>> >>>> It's in Mips16ISelDagToDag.cpp >>>> >>>> these two have to be together because they are both part of a complex pc >> relative calculation. &gt...
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...ve two machine instructions that I need to be together. >>>>> >>>>> BuildMI(MBB, I, DL, TII.get(Mips::LiRxImmAlignX16), V0) >>>>> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_HI); >>>>> BuildMI(MBB, I, DL, TII.get(Mips::AddiuRxPcImmX16), V1) >>>>> .addExternalSymbol("_gp_disp", MipsII::MO_ABS_LO); >>>>> >>>>> It's in Mips16ISelDagToDag.cpp >>>>> >>>>> these two have to be together because they are both part of a complex pc >>>...
2012 Aug 30
1
[LLVMdev] PHI
...ects: fi#0: size=4, align=4, at location [SP-8] fi#1: size=4, align=4, at location [SP-12] fi#2: size=4, align=4, at location [SP-4] Function Live Outs: %V0 BB#0: derived from LLVM BB %entry %V0<def> = LiRxImmX16 <es:_gp_disp>[TF=5] SaveRaF16 32 %V1<def> = AddiuRxPcImmX16 <es:_gp_disp>[TF=6] %V0<def> = SllX16 %V0<kill>, 16 %S0<def> = AdduRxRyRz16 %V1<kill>, %V0<kill> %V0<def> = LiRxImmX16 0 SwRxRyOffMemX16 %V0, %SP, 24; mem:ST4[%retval] SwRxRyOffMemX16 %V0<kill>, %SP, 20; mem:ST4[%i] PHI &...