Changes in ImportContext-Not-parameter-set.ll

5c028081 - [polly] Introduce -polly-print-* passes to replace -analyze.

Mon, 14 Mar 2022 13:39:25 +0000

[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 List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll

4ad76852 - Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`"""

Wed, 12 Feb 2020 07:01:35 +0000

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. List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll

17122ec1 - Revert "Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`""""

Thu, 13 Feb 2020 18:08:05 +0000

Revert "Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`""""This reverts commit bb51d243308dbcc9a8c73180ae7b9e47b98e68fb. List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll

bb51d243 - Revert "Revert "Reland "[Support] make report_fatal_error `abort` instead of `exit`"""

Wed, 12 Feb 2020 07:01:35 +0000

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 List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll

c3bcdc2f - [JSON] Make the failure to parse a jscop file a hard error

Thu, 10 Aug 2017 14:53:25 +0000

[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 List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll

e40c0fe3 - [tests] Set -polly-import-jscop-dir=%S always

Tue, 11 Jul 2017 10:39:01 +0000

[tests] Set -polly-import-jscop-dir=%S alwaysThis simplifies the test cases.llvm-svn: 307645 List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll

cb58bd6c - [JSONImporter] misses checks whether the data it imports makes sense.

Wed, 24 May 2017 15:09:35 +0000

[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 Differential Revision: https://reviews.llvm.org/D32739llvm-svn: 303759 List of files: /llvm-project-15.0.7/polly/test/JSONExporter/ImportContext/ImportContext-Not-parameter-set.ll