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++/60277] Bogus "inline function virtual ..." used but never defined
Date: Fri, 03 Dec 2021 05:45:43 +0000 [thread overview]
Message-ID: <bug-60277-4-jnvtHKmtst@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60277-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60277
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.3
Resolution|--- |FIXED
Status|NEW |RESOLVED
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=92695
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Fixed in GCC 9.3.0+ and in GCC 10 by r10-5027-g99150b053e1 and
r9-8069-ge3edafbca9f3553 (PR 92695). The patch includes exactly a testcase
which is similar enough to this one.
So closing as fixed.
prev parent reply other threads:[~2021-12-03 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 19:57 [Bug c++/60277] New: " ppluzhnikov at google dot com
2014-02-19 21:07 ` [Bug c++/60277] " nlewycky at google dot com
2014-02-21 14:57 ` jason at gcc dot gnu.org
2021-12-03 5:45 ` pinskia at gcc dot gnu.org [this message]
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-60277-4-jnvtHKmtst@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).