search for: mo_abs_hi

Displaying 6 results from an estimated 6 matches for "mo_abs_hi".

[LLVMdev] forcing two instructions to be together
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...be applied, depending on exactly what the constraints 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 h...
[LLVMdev] forcing two instructions to be together
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...hat 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 par...
[LLVMdev] forcing two instructions to be together
2013 Sep 17
0
[LLVMdev] forcing two instructions to be together
...exactly what the constraints 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 cal...
[LLVMdev] forcing two instructions to be together
2013 Sep 18
2
[LLVMdev] forcing two instructions to be together
...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 becau...
[LLVMdev] forcing two instructions to be together
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...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 becau...
[LLVMdev] forcing two instructions to be together
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...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 h...