public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100754] Order of multiple inheritance can lead to illegal code jump
Date: Wed, 26 May 2021 06:43:13 +0000	[thread overview]
Message-ID: <bug-100754-4-NMJtprlDFo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100754-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
IIRC inheritance across shared library borders is problematic.  You might want
to check how vtables resolve.

  reply	other threads:[~2021-05-26  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 15:22 [Bug c++/100754] New: " mgaron at pleora dot com
2021-05-26  6:43 ` rguenth at gcc dot gnu.org [this message]
2021-05-26 19:44 ` [Bug c++/100754] " mgaron at pleora dot com
2021-05-31 12:41 ` mgaron at pleora dot com
2021-05-31 12:41 ` mgaron at pleora dot com
2024-03-27  4:31 ` [Bug target/100754] " pinskia 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-100754-4-NMJtprlDFo@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).