David Blaikie f85e6da6d0 Fix instruction debug info location during legalization ... I found this from a particular GDB test suite case of inlining (something similar is provided as a test case) but came across a few other related cases (other callers of the same functions, and one other instance of the same coding mistake in a separate function). I'm not sure what the best way to test this is (let alone to cover the other cases I discovered), so hopefully this sufficies - open to ideas. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@206130 91177308-0d34-0410-b5e6-96231b3b80d8		2014-04-13 06:39:55 +00:00
..
Analysis	in findGCD of multiply expr return the gcd	2014-04-08 21:21:05 +00:00
Assembler
Bindings
Bitcode	AsmParser: add a warning for compatibility parsing	2014-04-05 22:42:53 +00:00
BugPoint
CodeGen	[PowerPC] Implement some additional TLI callbacks	2014-04-12 21:52:38 +00:00
DebugInfo	Fix instruction debug info location during legalization	2014-04-13 06:39:55 +00:00
ExecutionEngine
Feature
FileCheck
Instrumentation
Integer
JitListener
Linker
LTO
MC	Don't lose the thumb bit by using relocations with sections.	2014-04-11 19:18:01 +00:00
Object	[yaml2obj][ELF] ELF Relocations Support.	2014-04-11 04:13:39 +00:00
Other	Add -pass-remarks flag to 'opt'.	2014-04-08 16:42:38 +00:00
TableGen
tools	tools: teach objdump about FILE aux records	2014-04-13 03:11:08 +00:00
Transforms	[ARM64] Never hoist the shift value of a shift instruction.	2014-04-12 02:53:51 +00:00
Unit
Verifier
YAMLParser
.clang-format
CMakeLists.txt
lit.cfg	ARM: update even more tests	2014-04-03 17:35:22 +00:00
lit.site.cfg.in
Makefile
Makefile.tests
TestRunner.sh