https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96117
Stephen changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108499
--- Comment #3 from Stephen ---
False positives with this will just lead to proliferation of -Wno-array-bounds,
which doesn't help.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108499
--- Comment #2 from Stephen ---
> There is no way to figure out for the compiler that theSize is not zero
> either.
There is no way for the compiler to figure out that theSize *is* zero.
We have warnings -Wmaybe-uninitialized and -Wuninitiali
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108499
Bug ID: 108499
Summary: False positive -Warray-bounds
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108416
Bug ID: 108416
Summary: False positive -Wdangling-pointer
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108385
Bug ID: 108385
Summary: false positive -Wfree-nonheap-object
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108197
--- Comment #2 from Stephen ---
Richard, are you saying this a bug in the boost code? It's not quite clear to
me from your message. Can you be more specific about what the bug is in that
case?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108197
Bug ID: 108197
Summary: -Wstringop-overread emitted on simple boost
small_vector code
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105968
Bug ID: 105968
Summary: GCC vectorizes but reports that it did not vectorize
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon