[Bug sanitizer/109991] New: stack-use-after-scope

2023-05-26 Thread igkper at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109991 Bug ID: 109991 Summary: stack-use-after-scope Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assign

[Bug c++/109991] stack-use-after-scope

2023-05-26 Thread igkper at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109991 --- Comment #3 from igk --- (In reply to Andrew Pinski from comment #2) > Dup of bug 98675. > > *** This bug has been marked as a duplicate of bug 98675 *** Thanks for looking into this. I haven't quite understood though. I'm trying to see i

[Bug c++/109991] stack-use-after-scope

2023-05-26 Thread igkper at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109991 --- Comment #5 from igk --- OK, becoming clearer, thanks. I'm just hoping for this to be diagnosed in some way. IIUC basically GCC doesn't diagnose the UB so it proceeds with constexpr eval just because it can, or so it thinks, and in the proces