[Bug c++/112350] gcc is not triggering a dangling reference indicating stack use after return with -fsanitize=address and optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350 --- Comment #2 from Mohamed --- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350=1 it's shown here that the warning is triggered by setting -O3 optimization level to 3. I don't know if such behavior is expected i.e. triggering warning is

[Bug c++/112350] New: gcc is not triggering a dangling reference indicating stack use after return

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350 Bug ID: 112350 Summary: gcc is not triggering a dangling reference indicating stack use after return Product: gcc Version: 13.2.0 Status: UNCONFIRMED

[Bug sanitizer/109446] Possible destination array overflow without diagnosis in memcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109446 --- Comment #1 from Mohamed --- correction to scenario II should pass by value as follows //void test(Bar b) // scenario II

[Bug sanitizer/109446] New: Possible destination array overflow without diagnosis in memcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109446 Bug ID: 109446 Summary: Possible destination array overflow without diagnosis in memcpy Product: gcc Version: 8.4.0 Status: UNCONFIRMED Severity: normal

[Bug sanitizer/109444] Possible array overflow without diagnosis in memcpy if called within a virtual method scenario

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109444 --- Comment #2 from Mohamed --- I guess you meant Bar, since Bar has the array member. But then for the sanitizer to intervene and diagnose are there conditions for alignment??

[Bug sanitizer/109444] New: Possible array overflow without diagnosis in memcpy if called within a virtual method scenario

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109444 Bug ID: 109444 Summary: Possible array overflow without diagnosis in memcpy if called within a virtual method scenario Product: gcc Version: 12.0 Status: UNCONFIRMED