https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115402
--- Comment #7 from Lewis Baker ---
This paper has now been published and is available at:
https://isocpp.org/files/papers/P3323R0.html
: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
See https://godbolt.org/z/q4jYvPaah
The following code-snippet fails to compile:
volatile int vi = 0
: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
I have been doing some research on implementations of std::atomic::notify_all()
and std::atomic::wait() as
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
Compiling the following code with GCC trunk and flags: -std=c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452
--- Comment #9 from Lewis Baker ---
> In terms of the standard do you think this is technically undefined behaviour?
Yes, I think this is something that Gor was looking into as a wording issue
that could do with some clarification.
I think the
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
In the implementation of stop_token the _Stop_state_t implements
reference-counting for tracking shared ownership of the stop-state.
This is done via
: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
See https://godbolt.org/z/9Kj9o8
Compile the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95736
Lewis Baker changed:
What|Removed |Added
CC||lewissbaker.opensource@gmai
Version: 10.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
The wording of [dcl.fct.def.coroutine]
: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
If an exception is thrown from any of the following:
- promise_type constructor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95599
--- Comment #3 from Lewis Baker ---
I don't think that whether or not the awaitables or operands to co_yield are
captured by reference / aliased should play into the sequencing of calls to the
destructor.
The destructors of temporaries should al
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95599
--- Comment #1 from Lewis Baker ---
Note there is also some different behaviour if we change the example slightly
by removing awaitable::~awaitable() and leaving the awaitable type with a
trivial destructor.
See https://godbolt.org/z/ff5Uvy
In
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
If I write the statement:
co_yield T{};
Then I expect the T
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
Compile the following code with GCC trunk with flags -std=c++2a -fcoroutines
See https://godbolt.org/z
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
Build the following code sample using GCC trunk.
Command-line flags: -std=c++2a -fcoroutines
--
#include
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
The following code fails to compile under GCC 10.0 and GCC trunk
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
If I have the following code:
--
#include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95017
--- Comment #1 from Lewis Baker ---
Created attachment 48487
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48487&action=edit
test.cpp
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
See https://godbolt.org/z/v-Tkvi
Given a simple coroutine generator type, if I compile the
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
See https://godbolt.org/z/QCXqeo
Compile the following source code with GCC trunk.
Flags: -std=c++20 -fcoroutines
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70790
Lewis Baker changed:
What|Removed |Added
CC||lewissbaker.opensource@gmai
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
Created attachment 47490
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47490&action=edit
Example program
Compil
: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
The current implementation of std::stop_token in trunk has a few issues that
make it non-conformant with regards to the latest draft specification N4842.
The
: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
See https://godbolt.org/z/BndP6r
Version: GCC trunk
24 matches
Mail list logo