https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101361
--- Comment #13 from Taiju Tsuiki ---
I saw a similar inaccurate -Wstringop-overread warning with a smaller
reproducer (attached).
https://wandbox.org/permlink/EPjH0ZPoA4EWky0e
Reproducing gcc was tip of trunk (
https://github.com/gcc-mirror/gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101361
Taiju Tsuiki changed:
What|Removed |Added
CC||mail+gnu at tzik dot jp
--- Comment #12
IRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gnu at tzik dot jp
Target Milestone: ---
In a repro case below, the lambda is wrongly handled as a constexpr and its
co_return causes a compile error,
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gnu at tzik dot jp
Target Milestone: ---
In a repro case below, `co_await ({auto x = future{}; x;});` causes an internal
compiler error.
https://wandbox.org/permlink/3jX83p34mVDfBgc1
The
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gnu at tzik dot jp
Target Milestone: ---
In the repro case below, `foo()` in `co_return false ? co_await foo() : 1;`
should not be evaluated, and we should not see "NOTREACHED&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62052
Taiju Tsuiki changed:
What|Removed |Added
CC||mail+gnu at tzik dot jp
--- Comment #5
