From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28642] vtable offset position seems wrong
Date: Fri, 03 Dec 2021 23:19:38 +0000 [thread overview]
Message-ID: <bug-28642-9487-8Dd8YSXyga@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 #4 from Ben Woodard <woodard at redhat dot com> ---
This is from the abixml from the gcc version of the library:
<function-decl name='~section'
mangled-name='_ZN7abigail3ini6config7sectionD4Ev'
filepath='../../../../Work/libabigail/src/abg-ini.cc' line='856' column='1'
visibility='default' binding='global' size-in-bits='64'>
<parameter type-id='type-id-20101' is-artificial='yes'/>
<parameter type-id='type-id-8712' is-artificial='yes'/>
<return type-id='type-id-3'/>
</function-decl>
</member-function>
<member-function access='public' destructor='yes'
vtable-offset='-1'>
<function-decl name='~section'
mangled-name='_ZN7abigail3ini6config7sectionD0Ev'
filepath='../../../../Work/libabigail/src/abg-ini.cc' line='856' column='1'
visibility='default' binding='global' size-in-bits='64'
elf-symbol-id='_ZN7abigail3ini6config7sectionD0Ev'>
<parameter type-id='type-id-20101' is-artificial='yes'/>
<parameter type-id='type-id-8712' is-artificial='yes'/>
<return type-id='type-id-3'/>
</function-decl>
</member-function>
<member-function access='public' destructor='yes'
vtable-offset='-1'>
<function-decl name='~section'
mangled-name='_ZN7abigail3ini6config7sectionD2Ev'
filepath='../../../../Work/libabigail/src/abg-ini.cc' line='856' column='1'
visibility='default' binding='global' size-in-bits='64'
elf-symbol-id='_ZN7abigail3ini6config7sectionD2Ev'>
<parameter type-id='type-id-20101' is-artificial='yes'/>
<parameter type-id='type-id-8712' is-artificial='yes'/>
<return type-id='type-id-3'/>
</function-decl>
</member-function>
There are the vtable-offsets being set to -1.
----
Here is the abixml for the clang version.
<member-function access='public' destructor='yes'
vtable-offset='0'>
<function-decl name='~section'
mangled-name='_ZN7abigail3ini6config7sectionD0Ev'
filepath='/home/ben/Shared/test/libabigail-test/l5/../../../Work/libabigail/include/abg-ini.h'
line='386' column='1' visibility='default' binding='global' size-in-bits='64'
elf-symbol-id='_ZN7abigail3ini6config7sectionD2Ev'>
<parameter type-id='type-id-19664' is-artificial='yes'/>
<return type-id='type-id-11'/>
</function-decl>
</member-function>
it does appear that the parameter is missing.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-03 23:19 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 ` [Bug default/28642] " woodard at redhat dot com
2021-12-02 0:36 ` 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 [this message]
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-8Dd8YSXyga@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).