Allow Polly at all optimization levels
Restricting Polly to -O3 does not make a lot of sense as it is opt-in anyway and users who specifically request it should get it. If this causes performance problems we should rather address them by scheduling the right cleanup passes then just prevent the user from trying. Also restricting Polly to -O3 made bugpoint not work with the -O3 flag and polly enabled. llvm-svn: 200208
This commit is contained in:
parent
24d7e669b3
commit
f20210940c
|
@ -307,16 +307,6 @@ registerPollyEarlyAsPossiblePasses(const llvm::PassManagerBuilder &Builder,
|
|||
if (!shouldEnablePolly(Builder.OptLevel))
|
||||
return;
|
||||
|
||||
// We only run Polly at optimization level '-O3'.
|
||||
//
|
||||
// This is to ensure that scalar overhead that may be introduced by Polly is
|
||||
// properly cleaned up by LLVM later on. We may reinvestigate this decision
|
||||
// later on.
|
||||
if (Builder.OptLevel != 3) {
|
||||
errs() << "Polly should only be run with -O3. Disabling Polly.\n";
|
||||
return;
|
||||
}
|
||||
|
||||
registerPollyPasses(PM);
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue