llvm-6502/lib/ExecutionEngine/JIT
Andrew Lenharth 6a9746127a Like constants, globals on some platforms are GOT relative. This means they have to be allocated
near the GOT, which new doesn't do.  So break out the allocate into a new function.

Also move GOT index handling into JITResolver.  This lets it update the mapping when a Lazy
function is JITed.  It doesn't managed the table, just the mapping.  Note that this is
still non-ideal, as any function that takes a function address should also take a GOT
index, but that is a lot of changes.  The relocation resolve process updates any GOT entry
it sees is out of date.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22537 91177308-0d34-0410-b5e6-96231b3b80d8
2005-07-28 12:44:13 +00:00
..
Intercept.cpp Remove trailing whitespace 2005-04-21 22:55:34 +00:00
JIT.cpp Like constants, globals on some platforms are GOT relative. This means they have to be allocated 2005-07-28 12:44:13 +00:00
JIT.h For PR540: 2005-07-12 15:51:55 +00:00
JITEmitter.cpp Like constants, globals on some platforms are GOT relative. This means they have to be allocated 2005-07-28 12:44:13 +00:00
Makefile Fix library name. 2004-10-28 05:37:24 +00:00
TargetSelect.cpp Remove trailing whitespace 2005-04-21 22:55:34 +00:00