public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mario at klebsch dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107019] New: -Wunused-but-set-variable false positive for static variable in lambda with boost Date: Fri, 23 Sep 2022 15:03:51 +0000 [thread overview] Message-ID: <bug-107019-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107019 Bug ID: 107019 Summary: -Wunused-but-set-variable false positive for static variable in lambda with boost Product: gcc Version: 11.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mario at klebsch dot de Target Milestone: --- I get a palse positive from -Wunused-but-set-variable with this little sample: #include <stdio.h> #include <boost/asio.hpp> int main(int argc, char *argv[]) { static const char *func = __FUNCTION__; boost::asio::io_service io_service; boost::asio::deadline_timer timer(io_service); timer.async_wait( [](auto) { printf("%s()\n", func); }); } ~/tmp $ g++ -Wall bug2.cpp -c -I boost_1_80_0/ bug2.cpp: In function ‘int main(int, char**)’: bug2.cpp:7:28: warning: variable ‘func’ set but not used [-Wunused-but-set-variable] 7 | static const char *func = __FUNCTION__; | ^~~~ ~/tmp $ If I do not call timer.async_wait() but some other function taking const std::function<void(const boost::system::error_code&)>& as parameter, the usage of func in the lambda is recognized correctly. 73, Mario
next reply other threads:[~2022-09-23 15:03 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-23 15:03 mario at klebsch dot de [this message] 2022-09-23 15:10 ` [Bug c++/107019] " mario at klebsch dot de 2022-09-23 16:18 ` 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-107019-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).