public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cfy1990 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105646] New: g++ does not raise xxx is used uninitialized warning under some conditions
Date: Wed, 18 May 2022 14:07:22 +0000	[thread overview]
Message-ID: <bug-105646-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105646
           Summary: g++ does not raise xxx is used uninitialized warning
                    under some conditions
           Product: gcc
           Version: 12.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: cfy1990 at gmail dot com
  Target Milestone: ---

g++ version: g++ (Compiler-Explorer-Build-gcc--binutils-2.38) 12.1.0
Code link: https://godbolt.org/z/5MansKa5c
Compile arguments: -std=c++11  -Wextra -Wall -O2

Code:

int f1();
int f2(){
    bool v2{v2}; // used uninitialized warning
    auto const & a = f1();
    return a;
}
int f3(){
    auto const & a = f1();
    bool v3{v3}; // no warning in g++, got uninitialized warning in clang
    return a;
}

             reply	other threads:[~2022-05-18 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 14:07 cfy1990 at gmail dot com [this message]
2022-05-18 14:13 ` [Bug c++/105646] " cfy1990 at gmail dot com
2022-09-29  8:24 ` [Bug tree-optimization/105646] g++ does not raise "xxx may be used uninitialized" warning on dead code when optimizing cvs-commit at gcc dot gnu.org
2022-09-29  8:24 ` rguenth at gcc dot gnu.org
2022-10-27  0:54 ` pinskia 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-105646-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: 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).