Do not run -O3 to canonicalize test case

This is not only not necessary, but in case -03 changes this can actually
cause arbitrarily failing test cases such as, e.g., a recent change by Chandler
that caused -O3 to unroll the loop body, which made the loop we wanted to
detect disappear and consequently this test case fail.

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@200204 91177308-0d34-0410-b5e6-96231b3b80d8
Remove other unneccessary uses of -O3 in the test suite

The polly test suite is now -O3 clean.

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@200205 91177308-0d34-0410-b5e6-96231b3b80d8
Do not test polybench with 'make check-polly'

Those test cases should be tested in the LLVM test suite. For Polly we should
extract regression tests for the individual passes.

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@200206 91177308-0d34-0410-b5e6-96231b3b80d8
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.

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@200208 91177308-0d34-0410-b5e6-96231b3b80d8
Remove an unused parameter

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@200209 91177308-0d34-0410-b5e6-96231b3b80d8