search for: mipsiseldagtodag

Displaying 5 results from an estimated 5 matches for "mipsiseldagtodag".

Did you mean: mipseiseldagtodag
2011 Jun 22
1
[LLVMdev] Mips backend -- Incorrect globaladdr/constpool address generation when bit 15 of address is set?
Hi All, In SVN head, MipsISelDAGToDAG.cpp has the following optimization: // Operand is a result from an ADD. if (Addr.getOpcode() == ISD::ADD) { // When loading from constant pools, load the lower address part in // the instruction itself. Example, instead of: // lui $2, %hi($CPI1_0) // addiu $2, $2, %lo($...
2009 Mar 18
2
[LLVMdev] Selecting FrameIndex
Hi All I'm having nightmares with FrameIndexes during my backend development :( I have ComplexPatterns defined for my two addressing modes (RR and RI). Most of the time, FrameIndex operands appear to be on load/store nodes, in which case everything works fine as my custom addressing modes matchers work fine. Unfortunately, I now have an add node which has a FrameIndex operand (this results
2014 Apr 03
5
[LLVMdev] comparing .o files from different build trees
...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/MipsRegisterInfo.o ../../recurse2be/build/./lib/Target/Mips/Release+Asserts/MipsRegisterInfo.o differ: byte 23542, line 29 ./lib/Target/Mips/Release+Asserts/Mi...
2013 Apr 01
0
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
...==// + +//===----------------------------------------------------------------------===// +// MipsDAGToDAGISel - MIPS specific code to select MIPS machine +// instructions for SelectionDAG operations. +//===----------------------------------------------------------------------===// + +#include "MipsISelDAGToDAG.h" +#include "MipsModuleISelDAGToDAG.h" +#include "llvm/Support/Casting.h" +#include "llvm/Support/Debug.h" +#include "llvm/Support/raw_ostream.h" + +namespace llvm { + +bool MipsModuleDAGToDAGISel::runOnMachineFunction(MachineFunction &MF) { + DEBU...
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