search for: mipsseiseldagtodag

...r different targets. + const MipsSubtarget &Subtarget; +}; + +/// createMipsISelDag - This pass converts a legalized DAG into a +/// MIPS-specific DAG, ready for instruction scheduling. +FunctionPass *createMipsModuleISelDag(MipsTargetMachine &TM); +} + +#endif diff --git a/lib/Target/Mips/MipsSEISelDAGToDAG.cpp b/lib/Target/Mips/MipsSEISelDAGToDAG.cpp index d6d2207..0fc3c5e 100644 --- a/lib/Target/Mips/MipsSEISelDAGToDAG.cpp +++ b/lib/Target/Mips/MipsSEISelDAGToDAG.cpp @@ -35,6 +35,11 @@ #include "llvm/Target/TargetMachine.h" using namespace llvm; +bool MipsSEDAGToDAGISel::runOnMachineFu...

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

...AG.o ../../recurse2be/build/./lib/Target/Mips/Release+Asserts/MipsISelDAGToDAG.o differ: byte 55133, line 72 ./lib/Target/Mips/Release+Asserts/MipsRegisterInfo.o ../../recurse2be/build/./lib/Target/Mips/Release+Asserts/MipsRegisterInfo.o differ: byte 23542, line 29 ./lib/Target/Mips/Release+Asserts/MipsSEISelDAGToDAG.o ../../recurse2be/build/./lib/Target/Mips/Release+Asserts/MipsSEISelDAGToDAG.o differ: byte 83281, line 94 ./lib/Target/Mips/InstPrinter/Release+Asserts/MipsInstPrinter.o ../../recurse2be/build/./lib/Target/Mips/InstPrinter/Release+Asserts/MipsInstPrinter.o differ: byte 51888, line 73 ./lib/Target...