[Bug c++/117204] New: [12/13/14/15 regression] After r12-2132-ga1108556677, bogus -Warray-bounds warnings in std::vector::back()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117204 Bug ID: 117204 Summary: [12/13/14/15 regression] After r12-2132-ga1108556677, bogus -Warray-bounds warnings in std::vector::back() Product: gcc Version: 15.0 Status: UNC

[Bug c++/117155] Bogus -Wdangling-reference warning after r13-3511-gd2249cd9adf

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155 --- Comment #3 from Dimitry Andric --- (In reply to Jonathan Wakely from comment #1) > (In reply to Dimitry Andric from comment #0) > > After r15-3941-g2531f014fb2364 ("c++: Implement -Wdangling-reference > > I think the correct commit is > r13

[Bug c++/117155] New: Bogus -Wdangling-reference warning after r13-3511-gd2249cd9adf

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117155 Bug ID: 117155 Summary: Bogus -Wdangling-reference warning after r13-3511-gd2249cd9adf Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 --- Comment #19 from Dimitry Andric --- (In reply to Francois-Xavier Coudert from comment #18) > First patch pushed as > https://gcc.gnu.org/git/?p=gcc.git;a=commit; > h=9970b576b7e4ae337af1268395ff221348c4b34a > (forgot to add the PR number, si

[Bug middle-end/111632] gcc fails to bootstrap when using libc++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632 Dimitry Andric changed: What|Removed |Added CC||dimitry@unified-streaming.c

[Bug tree-optimization/102435] gcc 9: aarch64 -ftree-loop-vectorize results in wrong code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102435 --- Comment #3 from Dimitry Andric --- Note, in the mean time Ubuntu updated their default gcc version for Ubuntu 20.04 to 9.4.0: https://packages.ubuntu.com/focal-updates/devel/gcc-9 so this issue won't be encountered there anymore. Thanks.

[Bug tree-optimization/113239] [13/14 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 --- Comment #8 from Dimitry Andric --- (In reply to Frank Ch. Eigler from comment #7) > Wonder if this similar but different diagnostic is closely related: ... > where the c++ code in question is a straight > > vector<> foo; > vector<>

[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 --- Comment #3 from Dimitry Andric --- Alright, I can confirm that adding --param=vrp1-mode=vrp makes the warning go away. However, this option is no longer recognized by gcc-14-6924-g00dea7e8c41. I assume the ranger mode is now the default, and

[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 Dimitry Andric changed: What|Removed |Added CC||amacleod at redhat dot com --- Comment

[Bug c++/113239] New: [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 Bug ID: 113239 Summary: [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector Product: gcc Version: 14.0 Status: UNCONFIRMED Severity

[Bug tree-optimization/102435] New: gcc 9: aarch64 -ftree-loop-vectorize results in wrong code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102435 Bug ID: 102435 Summary: gcc 9: aarch64 -ftree-loop-vectorize results in wrong code Product: gcc Version: 9.4.1 Status: UNCONFIRMED Severity: normal P