Refactor signpost code to be safer, more debuggable #1461
Closed
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.
Now that we're all-C++, we can use
static constexpr bool
like this to still verify that something would build if the bool were either way, but still strip code that is unreachable.This fixes warnings about availability when profiling, and it makes the profiling code more readable & syntax highlighted, and it makes sure that you can't break profiling builds inadvertently.
Confirmed that even in debug mode, unreachable code is totally stripped and the entire
ASSignpost*
function call is not even present at all in the disassembly unless PROFILE=1.Over time I'd like us to move away from macros when it makes sense.