Evan Cheng b0b53491ef For some targets, it's not possible to place GVs in the same memory buffer as the MachineCodeEmitter allocated memory. Code and data has different read / write / execution privilege requirements. ... This is a short term workaround. The current solution is for the JIT memory manager to manage code and data memory separately. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@58688 91177308-0d34-0410-b5e6-96231b3b80d8		2008-11-04 09:30:48 +00:00
..
CMakeLists.txt
Intercept.cpp
JIT.cpp	For some targets, it's not possible to place GVs in the same memory buffer as the MachineCodeEmitter allocated memory. Code and data has different read / write / execution privilege requirements.	2008-11-04 09:30:48 +00:00
JIT.h	Support for allocation of TLS variables in the JIT. Allocation of a global	2008-10-25 15:41:43 +00:00
JITDwarfEmitter.cpp
JITDwarfEmitter.h
JITEmitter.cpp	Silence a compiler warning.	2008-11-03 07:14:02 +00:00
JITMemoryManager.cpp	fix a tricky bug in the JIT global variable emitter, that was triggered when JITing a variable independently of a function. This lead to sharing memory memory between functions and GVs thus changing the value of a GV could change the code in execution. more details on the ML.	2008-10-21 11:42:16 +00:00
Makefile
TargetSelect.cpp