public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vanyacpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102335] New: gcc misses -Wunused-value Date: Tue, 14 Sep 2021 18:11:12 +0000 [thread overview] Message-ID: <bug-102335-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102335 Bug ID: 102335 Summary: gcc misses -Wunused-value Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: vanyacpp at gmail dot com Target Milestone: --- struct mytype { int memfun [[gnu::pure]] (); }; void test() { mytype x; x.memfun(); // -Wunused-value mytype().memfun(); // no -Wunused-value } https://godbolt.org/z/vc49jWGqn The code above contains two usages of a [[gnu::pure]] function with ignored return value. GCC detect only the first one. I believe the second one deserves a warning too. Clang shows a warning on both usages.
next reply other threads:[~2021-09-14 18:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-14 18:11 vanyacpp at gmail dot com [this message] 2021-09-14 18:15 ` [Bug c++/102335] " pinskia at gcc dot gnu.org 2021-09-14 18:17 ` pinskia at gcc dot gnu.org 2021-09-15 8:03 ` rguenth 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-102335-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).