19afbfe331
Polly-ACC is unmaintained and since it has never been ported to the NPM pipeline, since D136621 it is not even accessible anymore without manually specifying the passes on the `opt` command line. Since there is no plan to put it to a maintainable state, remove it from Polly. Reviewed By: grosser Differential Revision: https://reviews.llvm.org/D142580
26 lines
980 B
ReStructuredText
26 lines
980 B
ReStructuredText
===========================================
|
|
Release Notes |release| |ReleaseNotesTitle|
|
|
===========================================
|
|
|
|
In Polly |version| the following important changes have been incorporated.
|
|
|
|
.. only:: PreRelease
|
|
|
|
.. warning::
|
|
These release notes are for the next release of Polly and describe
|
|
the new features that have recently been committed to our development
|
|
branch.
|
|
|
|
|
|
- Support for -polly-vectorizer=polly has been removed. Polly's internal
|
|
vectorizer is not well maintained and is known to not work in some cases
|
|
such as region ScopStmts. Unlike LLVM's LoopVectorize pass it also does
|
|
not have a target-dependent cost heuristics, and we recommend using
|
|
LoopVectorize instead of -polly-vectorizer=polly.
|
|
|
|
In the future we hope that Polly can collaborate better with LoopVectorize,
|
|
like Polly marking a loop is safe to vectorize with a specific simd width,
|
|
instead of replicating its functionality.
|
|
|
|
- Polly-ACC has been removed.
|