[Bug c++/86769] g++ destroys condition variable in for statement too early

2025-02-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 --- Comment #10 from Andrew Pinski --- Created attachment 60356 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60356&action=edit A Scalar testcase which shows this is a regression from GCC 4.9.x now

[Bug c++/86769] g++ destroys condition variable in for statement too early

2025-02-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 --- Comment #9 from Andrew Pinski --- Created attachment 60355 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60355&action=edit Another testcase

[Bug c++/86769] g++ destroys condition variable in for statement too early

2025-02-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Andrew Pinski changed: What|Removed |Added CC||xiaohuba2021 at 163 dot com --- Comment

[Bug c++/86769] g++ destroys condition variable in for statement too early

2025-01-29 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Marek Polacek changed: What|Removed |Added Assignee|mpolacek at gcc dot gnu.org|unassigned at gcc dot gnu.org

[Bug c++/86769] g++ destroys condition variable in for statement too early

2024-03-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Andrew Pinski changed: What|Removed |Added CC||gnu4u at flonatel dot org --- Comment #7

[Bug c++/86769] g++ destroys condition variable in for statement too early

2024-03-12 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 --- Comment #6 from Andrew Pinski --- Created attachment 57684 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57684&action=edit Testcase from godbolt

[Bug c++/86769] g++ destroys condition variable in for statement too early

2021-01-14 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 --- Comment #5 from Marek Polacek --- Further poking revealed that the patch above mishandles // PR c++/86769 // { dg-do run } #define assert(X) do { if (!(X)) __builtin_abort(); } while(0) int g; struct X { X() { g++; } ~X() { g--; } o

[Bug c++/86769] g++ destroys condition variable in for statement too early

2021-01-14 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Marek Polacek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned a

[Bug c++/86769] g++ destroys condition variable in for statement too early

2020-11-30 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment

[Bug c++/86769] g++ destroys condition variable in for statement too early

2020-10-28 Thread arthur.j.odwyer at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Arthur O'Dwyer changed: What|Removed |Added CC||arthur.j.odwyer at gmail dot com --- C

[Bug c++/86769] g++ destroys condition variable in for statement too early

2020-10-28 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Marek Polacek changed: What|Removed |Added CC||gcc-bugzilla at contacts dot eelis

[Bug c++/86769] g++ destroys condition variable in for statement too early

2018-08-01 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 Jonathan Wakely changed: What|Removed |Added Keywords||wrong-code Status|UNCONFIR

[Bug c++/86769] g++ destroys condition variable in for statement too early

2018-07-31 Thread richard-gccbugzilla at metafoo dot co.uk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769 --- Comment #1 from Richard Smith --- For easy reproduction: https://godbolt.org/g/dfZFxz This does not appear to be a regression: this example appears to be miscompiled by every version of GCC back to at least 4.1.