Move InstKinds out to their own vector. #4683
Open
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.
This is intended to make InstKind consume a quarter the current space (1 byte instead of 4). The expectation is this'll be roughly performance neutral, although we can start changing things to enable better performance for things that are happy to only examine the InstKind.
For a file generated by
source_gen
, before (with the mem usage fix):After:
And for
bazel run -c opt :compile_benchmark -- --benchmark_filter=Check
, before:Without
InstStore::Is
changes:With
InstStore::Is
changes:Note, benchmarks on my machine are expected to be noisy. But it does look like an incremental performance decrease in this test case.