Displaying 9 results from an estimated 9 matches for "mips16iseldagtodag".
2013 Apr 01
0
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
...ips/CMakeLists.txt
@@ -32,6 +32,8 @@ add_llvm_target(MipsCodeGen
MipsLongBranch.cpp
MipsMCInstLower.cpp
MipsMachineFunction.cpp
+ MipsModuleISelDAGToDAG.cpp
+ MipsModuleISelLowering.cpp
MipsRegisterInfo.cpp
MipsSEFrameLowering.cpp
MipsSEInstrInfo.cpp
diff --git a/lib/Target/Mips/Mips16ISelDAGToDAG.cpp b/lib/Target/Mips/Mips16ISelDAGToDAG.cpp
index 00b3449..2ffd3a9 100644
--- a/lib/Target/Mips/Mips16ISelDAGToDAG.cpp
+++ b/lib/Target/Mips/Mips16ISelDAGToDAG.cpp
@@ -35,6 +35,11 @@
#include "llvm/Target/TargetMachine.h"
using namespace llvm;
+bool Mips16DAGToDAGISel::runOnMachineFu...
2013 Apr 01
3
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
On Thu, Mar 28, 2013 at 12:22 PM, Nadav Rotem <nrotem at apple.com> wrote:
> IMHO the right way to handle target function attributes is to
> re-initialize the target machine and TTI for every function (if the
> attributes changed). Do you have another solution in mind ?
I don't really understand this.
TargetMachine and TTI may be quite expensive to initialize. Doing so for
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...ogether.
>
> 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 a pseudo instruction that is broken up imme...
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
...t(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...
2013 Sep 17
0
[LLVMdev] forcing two instructions to be together
...uildMI(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 a pseudo instruction that...
2013 Sep 18
2
[LLVMdev] forcing two instructions to be together
...gnX16), 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. An...
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...gnX16), 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. An...
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
...t;>>> .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 i...
2014 Apr 03
5
[LLVMdev] comparing .o files from different build trees
...64/AsmParser/Release+Asserts/ARM64AsmParser.o differ: byte 415950, line 573
./lib/Target/ARM64/Disassembler/Release+Asserts/ARM64Disassembler.o ../../recurse2be/build/./lib/Target/ARM64/Disassembler/Release+Asserts/ARM64Disassembler.o differ: byte 185919, line 1203
./lib/Target/Mips/Release+Asserts/Mips16ISelDAGToDAG.o ../../recurse2be/build/./lib/Target/Mips/Release+Asserts/Mips16ISelDAGToDAG.o differ: byte 59954, line 71
./lib/Target/Mips/Release+Asserts/MipsISelDAGToDAG.o ../../recurse2be/build/./lib/Target/Mips/Release+Asserts/MipsISelDAGToDAG.o differ: byte 55133, line 72
./lib/Target/Mips/Release+Asserts/...