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
diff --git a/tools/lli/lli.cpp b/tools/lli/lli.cpp
index 12f9155..0337703 100644
--- a/tools/lli/lli.cpp
+++ b/tools/lli/lli.cpp
@@ -132,10 +132,13 @@
}
EngineBuilder builder(MP);
- builder.setErrorStr(&ErrorMsg)
- .setEngineKind(ForceInterpreter
+ builder.setErrorStr(&ErrorMsg);
+ builder.setEngineKind(ForceInterpreter
? EngineKind::Interpreter
: 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 (!TargetTriple.empty())