public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/114254] [11/12/13 regression] Indirect inlining through C++ member pointers fails if the underlying class has a virtual function
Date: Wed, 20 Mar 2024 16:18:08 +0000	[thread overview]
Message-ID: <bug-114254-4-3g6jaGWhgy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114254-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114254

Martin Jambor <jamborm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11/12/13/14 regression]    |[11/12/13 regression]
                   |Indirect inlining through   |Indirect inlining through
                   |C++ member pointers fails   |C++ member pointers fails
                   |if the underlying class has |if the underlying class has
                   |a virtual function          |a virtual function

--- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed on trunk.  I may consider backporting to GCC 13 but probably not to
earlier versions.

      parent reply	other threads:[~2024-03-20 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 15:40 [Bug ipa/114254] New: " jamborm at gcc dot gnu.org
2024-03-07  8:08 ` [Bug ipa/114254] [11/12/13/14 regression] " rguenth at gcc dot gnu.org
2024-03-08 14:57 ` jamborm at gcc dot gnu.org
2024-03-19 21:38 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:18 ` jamborm 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-114254-4-3g6jaGWhgy@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).