Improve binary sizes by not globing MLIR dialects/passes #2414
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
By not globing all MLIR dialects/passes, many of which CUDAQ does not use, we can significantly improve binary sizes:
This change also improves compilation time when building
llvm
along with CUDAQ, instead of using a pre-built version for llvm. It also improves the--help
output for thecudaq-*
tools, as they won't be "polluted" with many passes/options that are not relevant in the context ofnvq++
.Improving the python bindings situation, which can possibly profit from a similar change, will be left to a later commit.
This PR is part of a series that address the long standing need to refactor the build system.