search for: emitjumptableinst

Hi Tim, Thank you for your answer. *We've fairly recently fixed a bug that looks very similar (r238680,which was well after 3.6)* If I wanted to back port that to 3.5 where should I look at? Where in the ARM backend the decision to relax an instruction is taken? *That's weird. Even with "-filetype=obj" (the bug only occurs whendirectly writing an object file)? Not that it

...m.org/viewvc/llvm-project?view=revision&revision=238680 >> >> Instruction relaxation rules should be in the TableGen files, I think, >> but that means it could be in a number of places. >> >> Step through lib/Target/ARM/ARMAsmPrinter.cpp, at >> ARMAsmPrinter::EmitJumpTableInsts and see what the operand is. >> >> You'd expect that it would be already relaxed by that point. If it is, >> the bug is in the printer. If not, it could be in the instruction >> selection process, either ARMISelLowering or during validation, at >> ARMISelDAGToDAG....