[Bug c++/108165] -Wdangling-reference false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108165 Sam Varshavchik changed: What|Removed |Added CC||mr...@courier-mta.com --- Comment #16

[Bug c++/109538] Spurious -Werror=dangling-reference false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109538 Sam Varshavchik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/109538] New: Spurious -Werror=dangling-reference false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109538 Bug ID: 109538 Summary: Spurious -Werror=dangling-reference false positive Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Componen

[Bug tree-optimization/100366] spurious warning - std::vector::clear followed by std::vector::insert(vec.end(), ...) with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100366 --- Comment #8 from Sam Varshavchik --- If the warning is spurious, then changing vector.tcc won't, of course, keep it from popping up elsewhere when the same sequence of events get triggered. Here, it drew my attention to the missed micro-opti

[Bug tree-optimization/100366] spurious warning - std::vector::clear followed by std::vector::insert(vec.end(), ...) with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100366 --- Comment #3 from Sam Varshavchik --- If the warning is justified then something else isn't adding up. I double-checked (with cppreference.com) something that I was pretty sure of: and an insert() at the end() iterator is valid. The insert()e

[Bug c++/100366] New: spurious warning - std::vector::clear followed by std::vector::insert(vec.end(), ...) with -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100366 Bug ID: 100366 Summary: spurious warning - std::vector::clear followed by std::vector::insert(vec.end(), ...) with -O2 Product: gcc Version: 11.1.0 Status: UNCONFIRMED