public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mohamed.selim at dxc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112350] gcc is not triggering a dangling reference indicating stack use after return with -fsanitize=address and optimization
Date: Mon, 06 Nov 2023 11:33:32 +0000	[thread overview]
Message-ID: <bug-112350-4-egvxW9eWdl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112350-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350

--- Comment #2 from Mohamed <mohamed.selim at dxc dot com> ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112350&GoAheadAndLogIn=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 coupled
with optimization level!!!

So the above link to compiler explorer example shows only the diagnostic error
from the sanitizer, if -O3 is added the warning is triggered.

      parent reply	other threads:[~2023-11-06 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 15:02 [Bug c++/112350] New: gcc is not triggering a dangling reference indicating stack use after return mohamed.selim at dxc dot com
2023-11-02 15:24 ` [Bug c++/112350] " pinskia at gcc dot gnu.org
2023-11-06 11:33 ` mohamed.selim at dxc dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-112350-4-egvxW9eWdl@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).