[llvm-dev] new pass manager version of opt vs. legacy pass manager version

[Snider, Todd via llvm-dev]

Hello All,

My development group has been maintaining a downstream version of the monorepo that stays in sync with the upstream "main" branch, but we are still using the legacy pass manager in our local copy of the monorepo.

We've recently encountered a few instances of lit tests that are failing when run with the legacy pass manager version of opt, but pass when run with the new pass manager version of opt.

The situation raises a couple of questions:

  *   Is the legacy pass manager behavior being adequately tested by the buildbots?
  *   What expectation should there be that legacy pass manager behavior will be maintained in light of changes made to code that affects both the new pass manager version and the legacy pass manager version of opt?

I suspect that my group is not the only ones trying to stay in sync with the upstream LLVM main branch and keep using the legacy pass manager, and I anticipate the only long-term remedy for our situation is to move to using the new pass manager as soon as we can.

Thoughts?

Regards.

Todd Snider
Texas Instruments Incorporated
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210422/2f3ff26f/attachment.html>