-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
GCC 13 reports OOB write #3533
Comments
danakj
added a commit
to danakj/subspace
that referenced
this issue
Jul 16, 2023
On GCC 12, a mutable variable can't be used in a constexpr context, but it now works in GCC 13. Unfortunately, (or fortunately?) GCC 13 reports an OOB write in fmtlib's float formatting. We disable that warning for now so that we can build, and it is reported upstream at fmtlib/fmt#3533
danakj
added a commit
to danakj/subspace
that referenced
this issue
Jul 17, 2023
On GCC 12, a mutable variable can't be used in a constexpr context, but it now works in GCC 13. Unfortunately, (or fortunately?) GCC 13 reports an OOB write in fmtlib's float formatting. We disable that warning for now so that we can build, and it is reported upstream at fmtlib/fmt#3533
danakj
added a commit
to chromium/subspace
that referenced
this issue
Jul 17, 2023
On GCC 12, a mutable variable can't be used in a constexpr context, but it now works in GCC 13. Unfortunately, (or fortunately?) GCC 13 reports an OOB write in fmtlib's float formatting. We disable that warning for now so that we can build, and it is reported upstream at fmtlib/fmt#3533
This warning doesn't make any sense because the capacity of that memory buffer is initialized from the |
Switched to a more reliable suppression in fb97cb2. Thanks for reporting. |
Thanks! |
This was referenced Dec 8, 2023
Upstream issue @ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109717 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repro: https://godbolt.org/z/on35ndoM4
This compiled okay on GCC 12, but when I updated to 13 I began receiving these errors about OOB write. The same happens on GCC trunk.
I am following the example in https://fmt.dev/latest/api.html#formatting-user-defined-types and forwarding formatting of a type to the formatter for its member. Doing so causes an OOB write error on GCC 13 with -O2 -NDEBUG flags.
Error is long:
The text was updated successfully, but these errors were encountered: