[Bug c++/118809] New: Excessive memory usage with global std::vector> in C++20 mode

2025-02-09 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118809 Bug ID: 118809 Summary: Excessive memory usage with global std::vector> in C++20 mode Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug c++/116506] [15 Regression] Destructors of temporary awaitables are executed too early

2024-10-17 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116506 --- Comment #4 from Dan Klishch --- SerenityOS's on-host tests seem to work fine with the patch attached here (this was the original reproducer) and one from PR116914. Without the later, I hit ICE similar to one outlined in the gimplify_var_or_p

[Bug c++/116506] New: [15 Regression] Destructors of temporary awaitables are executed too early

2024-08-27 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116506 Bug ID: 116506 Summary: [15 Regression] Destructors of temporary awaitables are executed too early Product: gcc Version: 15.0 Status: UNCONFIRMED Keywords: c++

[Bug c++/116502] [15 Regression] -Wunused-result warning cannot be suppressed if coroutine awaiter returns a reference after r15-2318-g2664c1bf83855b

2024-08-27 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116502 --- Comment #2 from Dan Klishch --- Can confirm that the patch fixes both the minified reproducer from the bug report and also the original reproducer (TestAsyncTestStreams from SerenityOS).

[Bug c++/116502] New: [15 Regression] -Wunused-result warning is not supressed if coroutine awaiter returns a reference

2024-08-27 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116502 Bug ID: 116502 Summary: [15 Regression] -Wunused-result warning is not supressed if coroutine awaiter returns a reference Product: gcc Version: 15.0 Status: UNCONFIRMED

[Bug c++/116482] New: Bogus -Wunused-parameter with C++ coroutines

2024-08-25 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116482 Bug ID: 116482 Summary: Bogus -Wunused-parameter with C++ coroutines Product: gcc Version: unknown Status: UNCONFIRMED Keywords: c++-coroutines Severity: normal

[Bug c++/115851] ICE in gimplify_var_or_parm_decl with coroutine suspension point inside statement expression

2024-08-25 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115851 --- Comment #1 from Dan Klishch --- GCC seems to do checks for coroutine-related types more eagerly now, so the original minified reproducer is rejected. Nonetheless, the underlying issue persists, which can be shown using this snippet: ``` #in

[Bug c++/115851] New: ICE in gimplify_var_or_parm_decl with coroutine suspension point inside statement expression

2024-07-09 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115851 Bug ID: 115851 Summary: ICE in gimplify_var_or_parm_decl with coroutine suspension point inside statement expression Product: gcc Version: unknown Status: UNCONFIRMED

[Bug fortran/115390] New: Bogus -Wuninitialized warning when using CHARACTER(*) argument in BIND(C) function

2024-06-07 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115390 Bug ID: 115390 Summary: Bogus -Wuninitialized warning when using CHARACTER(*) argument in BIND(C) function Product: gcc Version: unknown Status: UNCONFIRMED Se

[Bug c++/101355] incorrect `this' in destructor calls when compiling coroutines with ubsan

2021-09-04 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101355 Dan Klishch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/101355] compiling coroutines with ubsan emits bogus -Wmaybe-uninitialized warnings

2021-07-16 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101355 --- Comment #2 from Dan Klishch --- GCC incorrectly gimplifies the program. The code that is causing the warning is in the coroutine's actor function: try { D.9829 = &frame_ptr->__p;

[Bug c++/101355] compiling coroutines with ubsan emits bogus -Wmaybe-uninitialized warnings

2021-07-06 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101355 --- Comment #1 from Dan Klishch --- Created attachment 51112 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51112&action=edit gcc with -v option output

[Bug c++/101355] New: compiling coroutines with ubsan emits bogus -Wmaybe-uninitialized warnings

2021-07-06 Thread daklishch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101355 Bug ID: 101355 Summary: compiling coroutines with ubsan emits bogus -Wmaybe-uninitialized warnings Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: nor