en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll#5c028081 [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/ScopInfo/wraping_signed_expr_7.ll Mon, 14 Mar 2022 13:39:25 +0000 Michael Kruse <llvm-project@meinersbur.de> http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll#066dbf3f Track assumptions and restrictions separatly In order to speed up compile time and to avoid random timeouts we now separately track assumptions and restrictions. In this context assumptions describe parameter valuations we need and restrictions describe parameter valuations we do not allow. During AST generation we create a runtime check for both, whereas the one for the restrictions is negated before a conjunction is build. Except the In-Bounds assumptions we currently only track restrictions.Differential Revision: http://reviews.llvm.org/D17247llvm-svn: 262328 List of files: /llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll Tue, 01 Mar 2016 13:06:28 +0000 Johannes Doerfert <doerfert@cs.uni-saarland.de> http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll#f4ee371e tests: Drop -polly-detect-unprofitable and -polly-no-early-exitThese flags are now always passed to all tests and need to be disabled ifnot needed. Disabling these flags, rather than passing them to almost alltests, significantly simplfies our RUN: lines.llvm-svn: 249422 List of files: /llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll Tue, 06 Oct 2015 15:36:44 +0000 Tobias Grosser <tobias@grosser.es> http://172.16.0.5:8080/history/llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll#883f8c1d Use modulo semantic to generate non-integer-overflow assumptions This will allow to generate non-wrap assumptions for integer expressions that are part of the SCoP. We compare the common isl representation of the expression with one computed with modulo semantic. For all parameter combinations they are not equal we can have integer overflows. The nsw flags are respected when the modulo representation is computed, nuw and nw flags are ignored for now. In order to not increase compile time to much, the non-wrap assumptions are collected in a separate boundary context instead of the assumed context. This helps compile time as the boundary context can become complex and it is therefor not advised to use it in other operations except runtime check generation. However, the assumed context is e.g., used to tighten dependences. While the boundary context might help to tighten the assumed context it is doubtful that it will help in practice (it does not effect lnt much) as the boundary (or no-wrap assumptions) only restrict the very end of the possible value range of parameters. PET uses a different approach to compute the no-wrap context, though lnt runs have shown that this version performs slightly better for us.llvm-svn: 247732 List of files: /llvm-project-15.0.7/polly/test/ScopInfo/wraping_signed_expr_7.ll Tue, 15 Sep 2015 22:52:53 +0000 Johannes Doerfert <doerfert@cs.uni-saarland.de>