public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc at cookiesoft dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99362] New: invalid unused result Date: Wed, 03 Mar 2021 15:36:23 +0000 [thread overview] Message-ID: <bug-99362-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99362 Bug ID: 99362 Summary: invalid unused result Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gcc at cookiesoft dot de Target Milestone: --- Target: arm The following code will emit a warning on arm 32 bit compilers: ``` struct S { [[nodiscard]] S() {} }; int main() { S s; } ``` ``` <source>: In function 'int main()': <source>:6:7: warning: ignoring return value of 'S::S()', declared with attribute 'nodiscard' [-Wunused-result] 6 | S s; | ^ <source>:2:19: note: declared here 2 | [[nodiscard]] S() {} | ^ <source>:6:7: warning: ignoring return value of 'S::S()', declared with attribute 'nodiscard' [-Wunused-result] 6 | S s; | ^ <source>:2:19: note: declared here 2 | [[nodiscard]] S() {} | ^ Compiler returned: 0 ``` ``` S s = {} ``` does not emit such warning. Does not emit a warning on x86 compiler though. Does not emit a warning on 9.x branch, seems to be a regression. Godbolt link: https://godbolt.org/z/4Kof1x
next reply other threads:[~2021-03-03 15:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-03 15:36 gcc at cookiesoft dot de [this message] 2021-03-03 15:52 ` [Bug c++/99362] " jakub at gcc dot gnu.org 2021-03-03 16:28 ` gcc at cookiesoft dot de 2021-03-03 17:37 ` harald at gigawatt dot nl 2021-03-03 19:16 ` [Bug c++/99362] [10/11 Regression] " jakub at gcc dot gnu.org 2021-03-03 19:44 ` jakub at gcc dot gnu.org 2021-03-04 15:05 ` cvs-commit at gcc dot gnu.org 2021-03-04 15:06 ` [Bug c++/99362] [10 " jakub at gcc dot gnu.org 2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:09 ` jakub at gcc dot gnu.org 2021-04-23 12:37 ` jakub 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-99362-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).