[PATCH] D102909: [NPM] Ability to add a pass before a previously registered one

[Arthur Eubanks via Phabricator via llvm-commits]

aeubanks added a comment.

In D102909#2776635 <https://reviews.llvm.org/D102909#2776635>, @pratlucas wrote:

> Hi @aeubanks,
> As I mentioned, this is mostly targeted on plugin passes. At the moment the NPM only offers the PassBuilder's callbacks level of granularity to control when a plugin pass should be run, which might not be sufficient on some cases. The goal was to provide a more fine grained control over this, allowing plugin implementations to run before other native or plugin passes that migth impact their behavior.
> Do you have any suggestions on alternative ways to achieve this? I'm not fond of using pass names here myself and would be more than happy to go for a different implementation.

I'd still like to understand exactly what you'd be using this for. As in why does some pass need to run before all other instances of some other pass?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D102909/new/

https://reviews.llvm.org/D102909