public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cuzdav at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105571] New: Spurious "set but not used" on static constexpr local, used in lambda Date: Wed, 11 May 2022 19:06:34 +0000 [thread overview] Message-ID: <bug-105571-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105571 Bug ID: 105571 Summary: Spurious "set but not used" on static constexpr local, used in lambda Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: cuzdav at gmail dot com Target Milestone: --- With -Wall, in every c++ language level on virtually every version of g++ as far back as 4.9, g++ warns ("variable 'THIS_IS_USED' set but not used") on the following complete code: template <typename IterT, typename FuncT> void for_each(IterT b, IterT e, FuncT f) { while (b != e) { f(*b++); } } volatile int sink; void xxx(int x) { sink = x; } void foo() { static constexpr auto THIS_IS_USED = 1; int arr[10]{1,2,3,4,5,6,7,8,9,10}; for_each(arr, arr+10, [](auto v) { xxx(THIS_IS_USED + v); }); } <source>: In function 'void foo()': <source>:15:27: warning: variable 'THIS_IS_USED' set but not used [-Wunused-but-set-variable] 15 | static constexpr auto THIS_IS_USED = 1; | ^~~~~~~~~~~~ Compiler returned: 0 https://godbolt.org/z/b1s5Yqb3r This appears to be related to the "auto" parameter in the lambda. Changing it to 'int' makes the problem go away.
next reply other threads:[~2022-05-11 19:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-11 19:06 cuzdav at gmail dot com [this message] 2022-05-26 18:38 ` [Bug c++/105571] " johelegp at gmail dot com 2022-05-26 18:39 ` johelegp at gmail dot com 2022-09-23 16:25 ` 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-105571-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).