https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110394
jackyguo18 at hotmail dot com changed:
What|Removed |Added
Status|WAITING |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110394
--- Comment #5 from jackyguo18 at hotmail dot com ---
@Andrew Pinski - Thanks, just confirmed that that was the issue.
Why doesn't GCC choose to delete the function (thus causing the weird
behaviour) early at lower optimization levels?
Seems
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110394
--- Comment #1 from jackyguo18 at hotmail dot com ---
Created attachment 55396
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55396=edit
.ii file which triggers the bug
I couldn't attach the original .ii file, so I had to compress it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110394
Bug ID: 110394
Summary: Lambda capture receives wrong value
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other