public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/88804] incorrect unused but set static variable in templated lambda Date: Fri, 23 Sep 2022 16:22:28 +0000 [thread overview] Message-ID: <bug-88804-4-cfVmYuDQqz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88804-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88804 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Inconsistently diagnosed |incorrect unused but set |unused but set static |static variable in |variable in lambda |templated lambda --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Another example where the warning happens but should not: void foo(int); template <class T> void call(T t) { t(0); } void bar() { static int x=3; call([]<typename t>(t){ foo(x); }); } Basically the templated lambda is causing the static variable not be marked ...
next prev parent reply other threads:[~2022-09-23 16:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88804-4@http.gcc.gnu.org/bugzilla/> 2021-08-17 9:01 ` [Bug c++/88804] Inconsistently diagnosed unused but set static variable in lambda pinskia at gcc dot gnu.org 2022-09-23 16:18 ` pinskia at gcc dot gnu.org 2022-09-23 16:22 ` pinskia at gcc dot gnu.org [this message] 2022-09-23 16:25 ` [Bug c++/88804] incorrect unused but set static variable in templated lambda pinskia at gcc dot gnu.org 2022-09-23 16:27 ` pinskia at gcc dot gnu.org 2023-04-26 12:46 ` fiesh at zefix dot tv
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-88804-4-cfVmYuDQqz@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).