-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix: Disable false warn for GGC 12 bound checking #5355
Conversation
cd933d2
to
ffaae21
Compare
There is a compiler error with GCC 12 discussed here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115824 This Pybind code triggers the bug and was causing our compiler tests to fail. To fix gem5 compilation for gcc 12 these warnings/errors have been suppressed for this code. This is a copy and paste of: pybind/pybind11#5355 Change-Id: I9344951ef00d121ea0b609f4faa13dfe09aabb3b
ffaae21
to
02c1292
Compare
(I'll reply quicker this time around. Sorry I didn't see your last commit until now.) |
There is a compiler error with GCC 12 discussed here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115824 This Pybind code triggers the bug and was causing our compiler tests to fail. To fix gem5 compilation for gcc 12 these warnings/errors have been suppressed for this code. This is a copy and paste of: pybind/pybind11#5355 Change-Id: I9344951ef00d121ea0b609f4faa13dfe09aabb3b
Issue: pybind#5224 The `internals.registered_types_py...` line in pybind11.h triggers a false-positive bounds checking warning in GCC 12. This is discussed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115824. The workaround implemented is taken from suggestions then refactored to use the `PYBIND11_WARNING_PUSH` and `PYBIND11_WARNING_POP` MACROS.
02c1292
to
ca69278
Compare
Your replies are lightening fast compared to my own :). I'm very impressed with Pybind's response to my fix given i'm an outsider to the project. Thank you for the feedback. I've reduced the comment. |
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.
Thanks!
Oh, could you please add a suggestion for a Changelog entry? See other open PRs for the template. |
I think I've added this correctly. I just update the PR description here, right? |
Yes, it gets collected from there. |
Description
Issue: #5224
The
internals.registered_types_py...
line in pybind11.h triggers afalse-positive bounds checking warning in GCC 12.
This is discussed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115824.
The workaround implemented is taken from suggestions then refactored to
use the
PYBIND11_WARNING_PUSH
andPYBIND11_WARNING_POP
MACROS.Suggested changelog entry: