From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28642] vtable offset position seems wrong
Date: Thu, 02 Dec 2021 00:30:20 +0000 [thread overview]
Message-ID: <bug-28642-9487-bMpGvb9LwD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28642-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28642
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
The removal of the int parameter to the virtual class destructor is probably a
second problem but that could be a bug in clang where it doesn't give virtual
destructors a parameter (I would have to look at the assembly) or it may be a
problem with the DWARF that clang generates for that function. I would have
thought that removing the parameter would have changed the C++ function name
mangling thus making the functions linkage name different. If the resulting
codegen didn't make a destructor which took the int, it would have serious ABI
implications that would break at execution time. This suggests to me that it is
more likely a clang DWARF generation bug.
Anyway, I think that the removal of the int parameter is a different problem
from the offset in the vtable.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-02 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 0:21 [Bug default/28642] New: " woodard at redhat dot com
2021-12-02 0:30 ` woodard at redhat dot com [this message]
2021-12-02 0:36 ` [Bug default/28642] " woodard at redhat dot com
2021-12-03 22:42 ` woodard at redhat dot com
2021-12-03 23:19 ` woodard at redhat dot com
2021-12-07 0:53 ` woodard at redhat dot com
2021-12-09 0:52 ` woodard at redhat dot com
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-28642-9487-bMpGvb9LwD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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).