add a frame-pointer build option for profiling - #59
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
zig build -Dframe-pointers(ormake release ZIG_FLAGS=-Dframe-pointers) keeps frame pointers in a release build sosampleon macOS can unwind it and produce a flat profile. Without it a ReleaseFast binary shows a singlestartframe and nothing else.This came out of profiling native call overhead. A prototype that ran natives in place from the fast loop cut
abs()in a loop from 72ns to 30ns per call, but no real-application harness moved, and it needed a carve-out for the top-level frame and careful placement to avoid perturbing unrelated handlers. It was not merged; the profile and its conclusions are recorded for the next attempt.