Change Backtrace::enabled atomic from SeqCst to Relaxed #212
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 mirrors rust-lang/rust#92139.
The atomic is not synchronizing anything outside of its own value, so we don't need the
Acquire
/Release
guarantee that all memory operations prior to the store are visible after the subsequent load, nor theSeqCst
guarantee of all threads seeing all of the sequentially consistent operations in the same order.Using
Relaxed
reduces the overhead ofBacktrace::capture()
in the case that backtraces are not enabled.