mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 11:13:28 +01:00
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
This commit is contained in:
parent
ec10fcbd04
commit
e872040bf1
@ -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())
|
||||
|
Loading…
Reference in New Issue
Block a user