Matthias Braun 40485c228c Move VariableDbgInfo from MachineModuleInfo to MachineFunction ...

VariableDbgInfo is per function data, so it makes sense to have it with
the function instead of the module.

This is a necessary step to have machine module passes work properly.

Differential Revision: https://reviews.llvm.org/D27186

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@288292 91177308-0d34-0410-b5e6-96231b3b80d8

2016-11-30 23:48:50 +00:00

..

CMakeLists.txt

[CMake] NFC. Updating CMake dependency specifications

2016-11-17 04:36:50 +00:00

LLVMBuild.txt

MIRParser/LLVMBuild.txt: Add MC for MCRegisterInfo::getDwarfRegNum().

2015-07-24 01:12:36 +00:00

MILexer.cpp

[MIRParser] Parse lane masks for register live-ins

2016-10-12 21:06:45 +00:00

MILexer.h

[MIRParser] Parse lane masks for register live-ins

2016-10-12 21:06:45 +00:00

MIParser.cpp

Move FrameInstructions from MachineModuleInfo to MachineFunction

2016-11-30 23:48:42 +00:00

MIParser.h

MIRParser: Add support for parsing vreg reg alloc hints

2016-11-15 00:03:14 +00:00

MIRParser.cpp

Move VariableDbgInfo from MachineModuleInfo to MachineFunction

2016-11-30 23:48:50 +00:00