[do not land] Support for Header File Generation in DTYPE Selective Build in OSS #11617
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.
Summary
Part of the process for enabling the dtype selective build flow requires a header file to be generated that includes information about kernel operators and their dtypes. This change adds support for generating this header file when operators are specified. This functionality is enabled via the command line flag:
-DEXECUTORCH_DTYPE_GEN_HEADER=ON
. When enabled, the resultantselected_op_variants.h
file will be generated.Test plan
Updated
examples/selective_build/test_selective_build.sh
to include an example function that shows how to enable dtype header generation. Runningbash ./examples/selective_build/test_selective_build.sh cmake
produces a header file atcmake-out/examples/selective_build/select_build_lib/selected_op_variants.h
which contains selective build information. Note, the example intest_selective_build.sh
currently does not have dtype information, however the functionality of this feature was verified on other tests (e.g. mv3). These tests will be included in a future PR after #11601 successfully merges.