public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109470] unexpected const & behavior Date: Tue, 11 Apr 2023 08:36:29 +0000 [thread overview] Message-ID: <bug-109470-4-5XtjxiWtz9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109470-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109470 --- Comment #2 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- With "-Wall -O1" this is diagnosed properly, but with a spurious maybe-uninitialized warning: In file included from /usr/include/c++/12.2.0/cassert:44, from t.c:2: t.c: In function 'int main()': t.c:17:11: warning: dangling pointer 'dst' to an unnamed temporary may be used [-Wdangling-pointer=] 17 | assert(dst <= MAX); | ^~~ t.c:16:24: note: unnamed temporary defined here 16 | const int& dst = Min(MAX, (int)lenght); | ~~~^~~~~~~~~~~~~~~~~~ t.c:16:24: warning: '<anonymous>' may be used uninitialized [-Wmaybe-uninitialized] With "-Wall -O2" only the spurious maybe-uninitialized warning is emitted, which is not very helpful. With "-Wall -O0" no warning at all (diagnosing this issue at least needs some IPA).
next prev parent reply other threads:[~2023-04-11 8:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-11 7:43 [Bug c++/109470] New: " johannes.kellner at wandelbots dot com 2023-04-11 8:25 ` [Bug c++/109470] " xry111 at gcc dot gnu.org 2023-04-11 8:36 ` xry111 at gcc dot gnu.org [this message] 2023-04-11 9:48 ` johannes.kellner at wandelbots dot com 2023-04-11 9:52 ` pinskia at gcc dot gnu.org 2023-04-11 9:56 ` redi at gcc dot gnu.org 2023-04-11 10:23 ` johannes.kellner at wandelbots dot com 2023-04-11 10:36 ` jakub at gcc dot gnu.org 2023-04-11 10:37 ` redi at gcc dot gnu.org
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-109470-4-5XtjxiWtz9@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).