perf: Use procedural macro to include expected measurements at compile time #1659
+423
−94
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.
Closes #1634
This is an alternative solution to the one proposed in #1646. Instead of relying on a custom build script to generate a rust module containing a hard-coded constant for the expected measurements, this PR introduces a procedural macro to generate the needed literals to statically instantiate the expected measurements. This allows us to load expected measurements at compile time simply by doing:
Side note: I noticed we didn't have a nice
TcbInfostruct to deserialize the JSON so a significant part of this PR is introducing that struct.