Skip to content

Fix stack tracking in wolfCrypt benchmark#9983

Open
Frauschi wants to merge 1 commit intowolfSSL:masterfrom
Frauschi:bench_stack_fix
Open

Fix stack tracking in wolfCrypt benchmark#9983
Frauschi wants to merge 1 commit intowolfSSL:masterfrom
Frauschi:bench_stack_fix

Conversation

@Frauschi
Copy link
Contributor

Fix stack memory tracking for the wolfCrypt benchmark. Previous numbers have been quite off. Found while obtaining PQC numbers on MCUs.

Also fixes some "unused variable" warnings.

This is, among others, used on the wolfDemo board to show these numbers on trade shows.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes stack high-water-mark tracking in the wolfCrypt benchmark so reported stack usage is more accurate on embedded targets, and reduces build warnings by tightening feature-guarded option handling.

Changes:

  • Adjust stack checkpointing to measure deltas relative to a baseline and report setup-vs-run stack usage as a peak (MAX) instead of summing.
  • Guard -mac_final/mac_stream under NO_HMAC and -aead_set_key/aead_set_key under HAVE_AESGCM to avoid unused-variable warnings.
  • Change BENCH_MIN_RUNTIME_SEC default literal to be explicitly double.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

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