llvm dev - Aug 2021 - [RFC] Deprecating the legacy pass manager for the optimization pipeline

On 2021-08-24, Arthur Eubanks via llvm-dev wrote:
>The new pass manager has been on by default since the 13 branch. Now that
>we've branched for 14, I'd like to start the process of deprecating
and
>removing legacy pass manager support for the optimization pipeline. This
>includes clang, opt, and lld LTO support.
>
>Note that this doesn't apply to the codegen pipeline since there's
no new
>pass manager support for that yet.
>
>Are there any objections?
"deprecating" and 'removing" are different.

For 14.0.0, do you plan that -DLLVM_ENABLE_NEW_PASS_MANAGER=off will
give a warning or will be completely unsupported?

I probably should have said "deprecating and removing".

My intention was to remove it completely. -DLLVM_ENABLE_NEW_PASS_MANAGER
wouldn't do anything and we'd remove the
-flegacy-pass-manaager/-fexperimental-new-pass-manager flags, as well as
the corresponding lld flags.

On Tue, Aug 24, 2021 at 12:02 PM Fangrui Song <maskray at google.com>
wrote:
> On 2021-08-24, Arthur Eubanks via llvm-dev wrote:
> >The new pass manager has been on by default since the 13 branch. Now
that
> >we've branched for 14, I'd like to start the process of
deprecating and
> >removing legacy pass manager support for the optimization pipeline.
This
> >includes clang, opt, and lld LTO support.
> >
> >Note that this doesn't apply to the codegen pipeline since
there's no new
> >pass manager support for that yet.
> >
> >Are there any objections?
>
> "deprecating" and 'removing" are different.
>
> For 14.0.0, do you plan that -DLLVM_ENABLE_NEW_PASS_MANAGER=off will
> give a warning or will be completely unsupported?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20210824/cca681e1/attachment.html>