[polly] Introduce -polly-print-* passes to replace -analyze.The `opt -analyze` option only works with the legacy pass manager and might be removed in the future, as explained in llvm.org/PR53733. T
[polly] Introduce -polly-print-* passes to replace -analyze.The `opt -analyze` option only works with the legacy pass manager and might be removed in the future, as explained in llvm.org/PR53733. This patch introduced -polly-print-* passes that print what the pass would print with the `-analyze` option and replaces all uses of `-analyze` in the regression tests.There are two exceptions: `CodeGen\single_loop_param_less_equal.ll` and `CodeGen\loop_with_condition_nested.ll` use `-analyze on the `-loops` pass which is not part of Polly.Reviewed By: aeubanksDifferential Revision: https://reviews.llvm.org/D120782
show more ...
Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`"""This reverts commit 80a34ae31125aa46dcad47162ba45b152aed968d with fixes.Previously, since bots turning on EXP
Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`"""This reverts commit 80a34ae31125aa46dcad47162ba45b152aed968d with fixes.Previously, since bots turning on EXPENSIVE_CHECKS are essentially turning onMachineVerifierPass by default on X86 and the fact thatinline-asm-avx-v-constraint-32bit.ll and inline-asm-avx512vl-v-constraint-32bit.llare not expected to generate functioning machine code, this would godown to `report_fatal_error` in MachineVerifierPass. Here passing`-verify-machineinstrs=0` to make the intent explicit.
Revert "Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`""""This reverts commit bb51d243308dbcc9a8c73180ae7b9e47b98e68fb.
Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`"""This reverts commit 80a34ae31125aa46dcad47162ba45b152aed968d with fixes.On bots llvm-clang-x86_64-expensive-c
Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`"""This reverts commit 80a34ae31125aa46dcad47162ba45b152aed968d with fixes.On bots llvm-clang-x86_64-expensive-checks-ubuntu andllvm-clang-x86_64-expensive-checks-debian only,llc returns 0 for these two tests unexpectedly. I tweaked the RUN line a littlebit in the hope that LIT is the culprit since this change is not in thecodepath these tests are testing.llvm\test\CodeGen\X86\inline-asm-avx-v-constraint-32bit.llllvm\test\CodeGen\X86\inline-asm-avx512vl-v-constraint-32bit.ll
[ScopBuilder] Make -polly-stmt-granularity=scalar-indep the default.Splitting basic blocks into multiple statements if there are nowadditional scalar dependencies gives more freedom to the schedul
[ScopBuilder] Make -polly-stmt-granularity=scalar-indep the default.Splitting basic blocks into multiple statements if there are nowadditional scalar dependencies gives more freedom to the scheduler, butmore statements also means higher compile-time complexity. Switch tofiner statement granularity, the additional compile time should belimited by the number of operations quota.The regression tests are written for the -polly-stmt-granularity=bbsetting, therefore we add that flag to those tests that break with thenew default. Some of the tests only fail because the statements arenamed differently due to a basic block resulting in multiple statements,but which are removed during simplification of statements withoutside-effects. Previous commits tried to reduce this effect, but it isnot completely avoidable.Differential Revision: https://reviews.llvm.org/D42151llvm-svn: 324169
[JSON] Make the failure to parse a jscop file a hard errorSummary:Before, if we fail to parse a jscop file, this will be reported as anerror and importing is aborted. However, this isn't actually
[JSON] Make the failure to parse a jscop file a hard errorSummary:Before, if we fail to parse a jscop file, this will be reported as anerror and importing is aborted. However, this isn't actually strongenough, since although the import is aborted, the scop has already beenmodified and is very likely broken. Instead, make this a hard failureand throw an LLVM error. This new behaviour requires small changes tothe tests for the legacy pass, namely using `not` to verify the error.Further, fixed the jscop file for thebase_pointer_load_is_inst_inside_invariant_1 testcase.Reviewed By: MeinersburSplit out of D36578.llvm-svn: 310599
[tests] Set -polly-import-jscop-dir=%S alwaysThis simplifies the test cases.llvm-svn: 307645
[JSONImport] Check, if the size of an imported array is positivellvm-svn: 306479
[JSONImporter] misses checks whether the data it imports makes sense.Without this patch, the JSONImporter did not verify if the data it loadswere correct or not (Bug llvm.org/PR32543). I add some
[JSONImporter] misses checks whether the data it imports makes sense.Without this patch, the JSONImporter did not verify if the data it loadswere correct or not (Bug llvm.org/PR32543). I add some checks in theJSONImporter class and some test cases.Here are the checks (and test cases) I added :JSONImporter::importContext- The "context" key does not exist.- The context was not parsed successfully by ISL.- The isl_set has the wrong number of parameters.- The isl_set is not a parameter set.JSONImporter::importSchedule- The "statements" key does not exist.- There is not the right number of statement in the file.- The "schedule" key does not exist.- The schedule was not parsed successfully by ISL.JSONImporter::importAccesses- The "statements" key does not exist.- There is not the right number of statement in the file.- The "accesses" key does not exist.- There is not the right number of memory accesses in the file.- The "relation" key does not exist.- The memory access was not parsed successfully by ISL.JSONImporter::areArraysEqual- The "type" key does not exist.- The "sizes" key does not exist.- The "name" key does not exist.JSONImporter::importArrays/!\ Do not check if there is an key name "arrays" because it is notconsidered as an error.All checks are already in place or implemented inJSONImporter::areArraysEqual.Contributed-by: Nicolas Bonfante <[email protected]>Differential Revision: https://reviews.llvm.org/D32739llvm-svn: 303759