Skip to content

Conversation

@andrey-golubev
Copy link
Contributor

Summary

Hardware registration in vpux-opt can happen differently. Instead of having a custom MlirOptMain, we can rely on the new additions to the MLIR, which allow to register custom options before parsing all options and before calling the MlirOptMain itself.

This way, our custom patch can be reverted. We only need to take an upstream patch that's going to be available in later LLVM versions.

JIRA ticket

Related PR in NPU Compiler and/or OpenVINO repository with sub-module update

  • PR-xxx

Other related tickets

List tickets for additional work, eg, something was found during review but you agreed to address it in another Jira

  • E-xxxxx

mlir-opt's registerAndParseCLIOptions() forces users to both register
default MLIR options and parse the command line string. Custom mlir-opt
implementations, however, may need to provide own options or own
parsing. It seems that separating the two functions makes it easier to
achieve necessary customizations.

For example, one can register "default" options, then register custom
options (not available in standard mlir-opt), then parse all of them.
Other cases include two-stage parsing where some additional options
become available based on parsed information (e.g. compilation target
can allow additional options to be present).
@andrey-golubev andrey-golubev requested a review from a team as a code owner November 13, 2025 10:16
@andrey-golubev
Copy link
Contributor Author

Ok, unfortunately, this idea does not fly. If we want to maintain decent --help, there must be another way.

@andrey-golubev andrey-golubev deleted the agolubev/vpux_opt_alignment branch November 13, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants