Optimizer: Do not accidentally set schedule to NULL

In case the domain of a statement is empty, the schedule optimizer set by
accident the schedule to a NULL pointer. This is incorrect. Instead, we set
it to an empty isl_map with zero schedule dimensions. We already checked for
this in our test cases, but unfortunately the test cases did not fail as
expected. The assert we add in this commit now ensures that the test cases
fail properly in case we regress on this again.

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

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@201887 91177308-0d34-0410-b5e6-96231b3b80d8
DCE: Switch to hybrid precise-unprecise analysis

Instead of giving a choice between a precise (but possibly very complex)
analysis and an approximative analysis we now use a hybrid approach which uses N
precise steps followed by one approximating step. The precision of the analysis
can be changed by increasing N. With a default of 'N' = 2, we get fully precise
results for our current test cases and should not run into performance problems
for more complex test cases. We can adjust this value when we got more
experience with this dead code elimination.

git-svn-id: https://llvm.org/svn/llvm-project/polly/trunk@201888 91177308-0d34-0410-b5e6-96231b3b80d8
Enable polyhedral dead code elimination by default

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