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] New: gcc is not triggering a dangling reference indicating stack use after return Date: Thu, 02 Nov 2023 15:02:07 +0000 [thread overview] Message-ID: <bug-112350-4@http.gcc.gnu.org/bugzilla/> (raw) 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 Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mohamed.selim at dxc dot com Target Milestone: --- Scenario A: gcc is not triggering a dangling reference indicating stack use after return, the address-sanitizer does trigger though. "==1==ERROR: AddressSanitizer: stack-use-after-return on" Scenario B: gcc triggers a warning "-Wreturn-local-addr" The sanitizers intervenes in both scenarios as expected, while gcc warnings in not triggered in scenario A. Looks like the reference_wrapper has something to do with it. compiler options used: -std=c++14 -Wframe-address -Wreturn-local-addr -Wall -Wextra -Wpedantic -fsanitize=address #include <iostream> #include <utility> // scenario A const int& foo() { int x = 234; std::reference_wrapper<int> s{x}; return s.get(); } // scenario B const int& foo() { int s = 234; return s; } int main() { const auto& f_res = foo(); std::cout << "result: " << f_res << "\n"; return 0; }
next reply other threads:[~2023-11-02 15:02 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-02 15:02 mohamed.selim at dxc dot com [this message] 2023-11-02 15:24 ` [Bug c++/112350] " pinskia at gcc dot gnu.org 2023-11-06 11:33 ` [Bug c++/112350] gcc is not triggering a dangling reference indicating stack use after return with -fsanitize=address and optimization mohamed.selim at dxc dot com
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@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: linkBe 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).