New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src: use uint32_t for process initialization flags enum #46427
base: main
Are you sure you want to change the base?
Conversation
|
Review requested:
|
52853ca
to
f3cffbd
Compare
|
Any reason why we don't make init_process_flags a uint64_t instead? (I hope we don't end up with > 32 options in the flags, but one never knows..) |
|
@joyeecheung The referenced PR switched this from uint64 to uint32 because the former isn’t always accessible as a lock-free atomic variable, that’s the reason here :) |
| @@ -432,6 +432,9 @@ void ResetSignalHandlers() { | ||
| } | ||
|
|
||
| static std::atomic<uint32_t> init_process_flags = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a comment here describing why we use a uint32_t?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, makes sense – done in c259b3b!


(Semver-major due to ABI change)
Refs: #45221