Eric Christopher aacfef65cf Move DataLayout back to the TargetMachine from TargetSubtargetInfo ... derived classes. Since global data alignment, layout, and mangling is often based on the DataLayout, move it to the TargetMachine. This ensures that global data is going to be layed out and mangled consistently if the subtarget changes on a per function basis. Prior to this all targets(*) have had subtarget dependent code moved out and onto the TargetMachine. *One target hasn't been migrated as part of this change: R600. The R600 port has, as a subtarget feature, the size of pointers and this affects global data layout. I've currently hacked in a FIXME to enable progress, but the port needs to be updated to either pass the 64-bitness to the TargetMachine, or fix the DataLayout to avoid subtarget dependent features. llvm-svn: 227113		2015-01-26 19:03:15 +00:00
..
CloneSubModule.cpp
CMakeLists.txt
IndirectionUtils.cpp
LLVMBuild.txt	Orc/LLVMBuild.txt: Prune redundant "Target" in libdeps.	2015-01-25 11:41:41 +00:00
Makefile
OrcMCJITReplacement.cpp
OrcMCJITReplacement.h	Move DataLayout back to the TargetMachine from TargetSubtargetInfo	2015-01-26 19:03:15 +00:00
OrcTargetSupport.cpp