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.

llvm-svn: 76291

1 files changed, 5 insertions, 2 deletions

diff --git a/llvm/tools/lli/lli.cpp b/llvm/tools/lli/lli.cpp
index 12f91558247..0337703ecf5 100644
--- a/llvm/tools/lli/lli.cpp
+++ b/llvm/tools/lli/lli.cpp
@@ -132,10 +132,13 @@ int main(int argc, char **argv, char * const *envp) {
   }
 
   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())