search for: mo_abs_lo

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

Did you mean: mo_abs_hi
[LLVMdev] forcing two instructions to be together
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...ne 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 way to join these two. Bundles is one way you can go. Another is to use...
[LLVMdev] forcing two instructions to be together
2013 Sep 17
2
[LLVMdev] forcing two instructions 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 way to join >...
[LLVMdev] forcing two instructions to be together
2013 Sep 17
0
[LLVMdev] forcing two instructions to be together
...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 way to join these two. > Bundles is one way you c...
[LLVMdev] forcing two instructions to be together
2013 Sep 18
2
[LLVMdev] forcing two instructions to be together
...t;>> 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 way to join...
[LLVMdev] forcing two instructions to be together
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...t;>> 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 way to join...
[LLVMdev] forcing two instructions to be together
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...t; 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 lookin...