-
Notifications
You must be signed in to change notification settings - Fork 528
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
NoNewGlobals for cache_mem_map #1781
Conversation
Revert MapLabel to a POD type. Detected by Coverity. CID 1554648: Initialization or destruction ordering is unspecified (GLOBAL_INIT_ORDER).
74203fe
to
4e95cfe
Compare
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.
Thank you for fixing it. I polished formatting and PR description for consistency (with nearby declarations and similar official commits).
I also adjusted PR title because we are not fixing MemStoreMap itself here, but I do not insist on that adjustment.
P.S. We need to adjust NoNewGlobals text to explicitly exclude built-in/intrinsic types that are not initialized using functions. This PR is an example of a use case that is excluded.
Co-authored-by: Alex Rousskov <[email protected]>
Detected by Coverity. CID 1554648: Initialization or destruction ordering is unspecified (GLOBAL_INIT_ORDER).
Detected by Coverity. CID 1554648: Initialization or destruction ordering is unspecified (GLOBAL_INIT_ORDER).
Detected by Coverity. CID 1554648: Initialization or destruction
ordering is unspecified (GLOBAL_INIT_ORDER).