Switch lli back to using allocate-gvs-with-code behavior.

- Otherwise we get two regressions in llvm-test for applications which run out
   of space.

 - Once the JIT memory manager is improved, this can be switched back.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@76291 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Daniel Dunbar 2009-07-18 08:07:13 +00:00
parent 3a4a884c16
commit 4dc31369eb

View File

@ -132,10 +132,13 @@ int main(int argc, char **argv, char * const *envp) {
} }
EngineBuilder builder(MP); EngineBuilder builder(MP);
builder.setErrorStr(&ErrorMsg) builder.setErrorStr(&ErrorMsg);
.setEngineKind(ForceInterpreter builder.setEngineKind(ForceInterpreter
? EngineKind::Interpreter ? EngineKind::Interpreter
: EngineKind::JIT); : EngineKind::JIT);
// FIXME: Don't allocate GVs with code once the JIT because smarter about
// memory management.
builder.setAllocateGVsWithCode(true);
// If we are supposed to override the target triple, do so now. // If we are supposed to override the target triple, do so now.
if (!TargetTriple.empty()) if (!TargetTriple.empty())