public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105423] Bogus -Werror=maybe-uninitialized with definitely initialized variable Date: Fri, 29 Apr 2022 06:33:28 +0000 [thread overview] Message-ID: <bug-105423-4-av8IgLDoBv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105423-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105423 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 Blocks| |24639 Last reconfirmed| |2022-04-29 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- I'm getting > ~/install/gcc-12/usr/local/bin/g++ -S t.ii -O -Werror=maybe-uninitialized t.ii: In instantiation of 'std::Trans_NS___cxx11_basic_string<_CharT, <template-parameter-1-2>, <template-parameter-1-3> >::Trans_NS___cxx11_basic_string() [with _CharT = char; _Traits = std::char_traits; <template-parameter-1-3> = char]': t.ii:54:49: required from here t.ii:37:37: error: no matching function for call to 'std::Trans_NS___cxx11_basic_string<char>::<unnamed struct>::._anon_0(std::allocator_traits<std::allocator<char> >::pointer)' 37 | Trans_NS___cxx11_basic_string() : _M_dataplus(_M_local_data()) {} | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ t.ii:25:10: note: candidate: 'std::Trans_NS___cxx11_basic_string<char>::<unnamed struct>::<constructor>()' 25 | struct { | ^ t.ii:25:10: note: candidate expects 0 arguments, 1 provided ... so the testcase doesn't compile for me Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 [Bug 24639] [meta-bug] bug to track all Wuninitialized issues
next prev parent reply other threads:[~2022-04-29 6:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 13:29 [Bug tree-optimization/105423] New: " byteslice at airmail dot cc 2022-04-29 6:33 ` rguenth at gcc dot gnu.org [this message] 2022-04-29 11:27 ` [Bug tree-optimization/105423] " byteslice at airmail dot cc 2022-10-31 23:45 ` 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-105423-4-av8IgLDoBv@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).