-
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
[BUG]: bounds checking problem #5224
Comments
Same problem.
|
We also get this arry-bounds[a] error when building [a]
|
I see the same error at https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=981519&view=results |
Ouch, we are also bitten by this. Does anyone know of a workaround until this is fixed (i.e. a compiler flag?). |
Adding I see both |
Thanks @jmeyers314 ! |
See pybind/pybind11#5224 Signed-off-by: wangjiezhe <wangjiezhe@gmail.com>
See pybind/pybind11#5224 Signed-off-by: wangjiezhe <wangjiezhe@gmail.com>
This is a bug in GCC 12 with GCC 12.4.0 libstdc++. Yeah, I also first found this by compiling pybind. |
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 in this discussion.
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 in this discussion. Signed-off-by: Bobby R. Bruce <bbruce@ucdavis.edu>
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 in this discussion.
I created a PR which fixes this issue. It's a bit of a work around but given the issue is with gcc 12, I don't see a better way. #5355 |
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.
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.
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.
Required prerequisites
What version (or hash if on master) of pybind11 are you using?
2.13.1
Problem description
When compiling contourpy with bounds checking (
-fstack-clash-protection
) enabled, I get a compilation error (because contourpy by default builds with-Werror
). That's with gcc 12.4.0 on NetBSD-10.99.11/amd64.I reported this to the contourpy project but they said it's a problem in pybind11.
Here's the compilation output:
I tried it also with pybind11 2.12.0, same problem there.
Reproducible example code
Is this a regression? Put the last known working version here if it is.
Not a regression
The text was updated successfully, but these errors were encountered: