public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mattreecebentley at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100956] New: Unused variable warnings ignore "if constexpr" blocks where variables are conditionally used Date: Tue, 08 Jun 2021 01:23:18 +0000 [thread overview] Message-ID: <bug-100956-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100956 Bug ID: 100956 Summary: Unused variable warnings ignore "if constexpr" blocks where variables are conditionally used Product: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: mattreecebentley at gmail dot com Target Milestone: --- For example, as part of a container class: void remove_memory_blocks(pointer back_element_in_final_block) { if constexpr(!std::is_trivially_destructible<element_type>::value) { // destroy each element in each memory block until the back_element is reached } // remove memory blocks } If element_type is_trivially_destructible, G++ will warn that back_element_in_final_block is unused every time the function is called. Ideally this warning should be performed before constexpr blocks are removed by a parser (I have no idea what the procedure is for GCC, I'm just guessing here)
next reply other threads:[~2021-06-08 1:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 1:23 mattreecebentley at gmail dot com [this message] 2021-06-08 12:35 ` [Bug c++/100956] " redi at gcc dot gnu.org 2021-06-09 0:14 ` mattreecebentley 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-100956-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).