[Bug c++/108683] Move Occurs when initializing an aggregate base

2023-02-06 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108683 --- Comment #2 from David Ledger --- Bar stores an int, it isn't empty.

[Bug c++/108683] New: Move Occurs when initializing an aggregate base

2023-02-06 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108683 Bug ID: 108683 Summary: Move Occurs when initializing an aggregate base Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Componen

[Bug c++/104177] coroutine frame is not being allocated with the correct alignment

2023-01-23 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104177 --- Comment #20 from David Ledger --- Yeah, your right. I had noticed the mistake and reduced the code without thinking enough: ```CPP #include #include #include #include using namespace std; struct overaligned { alignas(128) char padding[

[Bug c++/104177] coroutine frame is not being allocated with the correct alignment

2023-01-20 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104177 --- Comment #16 from David Ledger --- The above example produces the xmm instruction on a clearly misaligned value. I was searching the assembly using: ```SH #!/bin/bash g++-11 main.cpp -std=c++2a -O3 -march=native -S grep -E "vmovdqu\s%xmm0,\

[Bug c++/104177] coroutine frame is not being allocated with the correct alignment

2023-01-20 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104177 David Ledger changed: What|Removed |Added CC||davidledger at live dot com.au --- Comme

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2023-01-19 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #12 from David Ledger --- (In reply to David Ledger from comment #11) > This did not occur with GCC 10.2, it started in GCC 10.3: > > 10.3 (https://godbolt.org/z/jrdv31M17): > ``` > 0x15d1ed3 A > 0x15d1ed2 ~A > 0x15d1ed3 ~A > ``` >

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2022-11-11 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #11 from David Ledger --- This did not occur with GCC 10.2, it started in GCC 10.3: 10.3 (https://godbolt.org/z/jrdv31M17): ``` 0x15d1ed3 A 0x15d1ed2 ~A 0x15d1ed3 ~A ``` 10.2 (https://godbolt.org/z/rrvKh9h6K): ``` 0x2322ed1 A 0x2322

[Bug c++/101367] [coroutines] destructor for capture in lambda temporary operand to co_yield expression called twice

2021-08-09 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101367 --- Comment #4 from David Ledger --- Yeah, I'm just saying I suspect the problem was still there with the empty capture list, its just not observable.

[Bug c++/100611] coroutines: destructor called too many times for coroutine lambda stored object

2021-08-08 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100611 --- Comment #4 from David Ledger --- It still seems like a bug though.

[Bug c++/101367] [coroutines] destructor for capture in lambda temporary operand to co_yield expression called twice

2021-08-08 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101367 David Ledger changed: What|Removed |Added CC||davidledger at live dot com.au --- Comme

[Bug c++/100772] Templated coroutine new function's arguments have incorrect value categories/overload selection

2021-07-09 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100772 --- Comment #1 from David Ledger --- Bump, is there anything else I need to provide to assist in this matter?

[Bug c++/98401] Temporaries passed to co_await sometimes cause an extraneous call to destructor at incorrect address

2021-06-10 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98401 David Ledger changed: What|Removed |Added CC||davidledger at live dot com.au --- Commen

[Bug c++/100611] coroutines: destructor called too many times for coroutine lambda stored object

2021-06-10 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100611 David Ledger changed: What|Removed |Added CC||davidledger at live dot com.au --- Comme

[Bug c++/99576] [coroutines] destructor of a temporary called too early within co_await expression

2021-06-10 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99576 David Ledger changed: What|Removed |Added CC||davidledger at live dot com.au --- Commen

[Bug c++/100772] New: Templated coroutine new function's arguments have incorrect value categories/overload selection

2021-05-26 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100772 Bug ID: 100772 Summary: Templated coroutine new function's arguments have incorrect value categories/overload selection Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-12-02 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #6 from David Ledger --- Is this the right place for me to track this bug?

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-10-28 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #4 from David Ledger --- @Iain Sandoe In terms of the standard do you think this is technically undefined behaviour? I tried bring this up with Std-Proposals but got no response at all. I believe either I'm very bad at writing (likel

[Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement

2020-10-16 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 David Ledger changed: What|Removed |Added CC||davidledger at live dot com.au --- Commen

[Bug c++/97433] New: C++20 Coroutines, Unexpected reordering of await_resume, return_value and yield_value

2020-10-14 Thread davidledger at live dot com.au via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97433 Bug ID: 97433 Summary: C++20 Coroutines, Unexpected reordering of await_resume, return_value and yield_value Product: gcc Version: 11.0 Status: UNCONFIRMED Seve