public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alvaro.begue at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108667] New: Spurious "maybe used uninitialized [-Wmaybe-uninitialized]" warning Date: Fri, 03 Feb 2023 22:02:29 +0000 [thread overview] Message-ID: <bug-108667-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108667 Bug ID: 108667 Summary: Spurious "maybe used uninitialized [-Wmaybe-uninitialized]" warning Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: alvaro.begue at gmail dot com Target Milestone: --- I am using g++-12.1.0 on x86-64, but g++-12.2.0 in godbolt.org shows the same problem The options are -O3 -Wmaybe-uninitialized . The code: #include <functional> struct S { S(std::function<void()> f) : f(f) {} std::function<void()> g; std::function<void()> f; }; int main() { S s([](){}); s.f(); } Compiler output (from godbolt.org): In file included from /opt/compiler-explorer/gcc-12.2.0/include/c++/12.2.0/functional:59, from <source>:1: In copy constructor 'std::function<_Res(_ArgTypes ...)>::function(const std::function<_Res(_ArgTypes ...)>&) [with _Res = void; _ArgTypes = {}]', inlined from 'S::S(std::function<void()>)' at <source>:4:34, inlined from 'int main()' at <source>:11:15: /opt/compiler-explorer/gcc-12.2.0/include/c++/12.2.0/bits/std_function.h:391:17: warning: '<anonymous>' may be used uninitialized [-Wmaybe-uninitialized] 391 | __x._M_manager(_M_functor, __x._M_functor, __clone_functor); | ~~~~^~~~~~~~~~ /opt/compiler-explorer/gcc-12.2.0/include/c++/12.2.0/bits/std_function.h: In function 'int main()': /opt/compiler-explorer/gcc-12.2.0/include/c++/12.2.0/bits/std_function.h:267:7: note: by argument 2 of type 'const std::_Any_data&' to 'static bool std::_Function_handler<_Res(_ArgTypes ...), _Functor>::_M_manager(std::_Any_data&, const std::_Any_data&, std::_Manager_operation) [with _Res = void; _Functor = main()::<lambda()>; _ArgTypes = {}]' declared here 267 | _M_manager(_Any_data& __dest, const _Any_data& __source, | ^~~~~~~~~~ <source>:11:15: note: '<anonymous>' declared here 11 | S s([](){}); | ^ Compiler returned: 0
next reply other threads:[~2023-02-03 22:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-03 22:02 alvaro.begue at gmail dot com [this message] 2023-02-04 0:07 ` [Bug tree-optimization/108667] Spurious "may be " pinskia at gcc dot gnu.org 2023-02-04 0:33 ` alvaro.begue at gmail dot com 2023-02-06 7:47 ` rguenth at gcc dot gnu.org 2023-02-06 15:19 ` alvaro.begue at gmail 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-108667-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).