public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99362] [10/11 Regression] invalid unused result
Date: Wed, 03 Mar 2021 19:16:46 +0000 [thread overview]
Message-ID: <bug-99362-4-liPVnRV2cJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99362-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99362
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Priority|P3 |P2
Last reconfirmed| |2021-03-03
Status|UNCONFIRMED |NEW
Target Milestone|--- |10.3
Summary|invalid unused result |[10/11 Regression] invalid
| |unused result
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Caused by r10-4001-g8ad0c477e888d34c8fc6dbcc008ef66505071d65
PR88146 fixed this for arm before, but then r10-4001 when implementing P1771R1
readded this for constructors. It is now needed for ctors too, but needs to
differentiate for them between the cases P1771R1 requires and normal
targetm.cxx.cdtor_returns_this construction.
next prev parent reply other threads:[~2021-03-03 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:36 [Bug c++/99362] New: " gcc at cookiesoft dot de
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 ` jakub at gcc dot gnu.org [this message]
2021-03-03 19:44 ` [Bug c++/99362] [10/11 Regression] " 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-liPVnRV2cJ@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: link
Be 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).