llvm-project/polly/test/JSONExporter/ImportSchedule
Philip Pfaffe c3bcdc2f1a [JSON] Make the failure to parse a jscop file a hard error
Summary:
Before, if we fail to parse a jscop file, this will be reported as an
error and importing is aborted. However, this isn't actually strong
enough, since although the import is aborted, the scop has already been
modified and is very likely broken. Instead, make this a hard failure
and throw an LLVM error. This new behaviour requires small changes to
the tests for the legacy pass, namely using `not` to verify the error.
Further, fixed the jscop file for the
base_pointer_load_is_inst_inside_invariant_1 testcase.

Reviewed By: Meinersbur

Split out of D36578.

llvm-svn: 310599
2017-08-10 14:53:25 +00:00
..
ImportSchedule-No-schedule-key.ll [JSON] Make the failure to parse a jscop file a hard error 2017-08-10 14:53:25 +00:00
ImportSchedule-Schedule-not-valid.ll [JSON] Make the failure to parse a jscop file a hard error 2017-08-10 14:53:25 +00:00
ImportSchedule-Statements-mispelled.ll [JSON] Make the failure to parse a jscop file a hard error 2017-08-10 14:53:25 +00:00
ImportSchedule-Wrong-number-statements.ll [JSON] Make the failure to parse a jscop file a hard error 2017-08-10 14:53:25 +00:00
is2___%for.cond---%for.end10.jscop
is3___%for.cond---%for.end10.jscop
is4___%for.cond---%for.end10.jscop
is___%for.cond---%for.end10.jscop