From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30260] add support for pointer-to-member types
Date: Thu, 30 Nov 2023 21:51:59 +0000 [thread overview]
Message-ID: <bug-30260-9487-zxFRIn4LaC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30260-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30260
--- Comment #6 from gprocida at google dot com ---
FWIW, STG diff output looks like this:
function symbol 'int struct S::* s2()' {_Z2s2v} was added
function symbol 'int s10(int struct S::*)' {_Z3s10M1Si} was added
function symbol 'void pmz_fun()' {_Z7pmz_funv} was added
variable symbol 'char struct Y::* pmc' was added
variable symbol 'int union U::* pmcu' was added
variable symbol 'double struct X::* pmd' was added
variable symbol 'void(struct X::* pmf)(struct X*, int)' was added
variable symbol 'int struct X::* pmi' was added
variable symbol 'int union U::* pmu' was added
variable symbol 'int struct { int t; }::* pmy' was added
variable symbol 'int struct S::* s0' was added
variable symbol 'int struct S::** s1' was added
variable symbol 'int struct S::*(* s3)()' was added
variable symbol 'int struct S::* s4[7]' was added
variable symbol 'int* struct S::* s5' was added
variable symbol 'int(* struct S::* s6)()' was added
variable symbol 'int(struct S::* s7)(struct S*)' was added
variable symbol 'int(struct S::* s8)[7]' was added
variable symbol 'const int struct S::* volatile s9' was added
variable symbol changed from 'char struct A::* diff' to 'int struct B::* diff'
type changed from 'char struct A::*' to 'int struct B::*'
containing type changed from 'struct A' to 'struct B'
type changed from 'char' to 'int'
If you have any better ideas than "containing type" and "type", I might steal
them. :-)
"pointed-to-member type"???
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-30 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 11:37 [Bug default/30260] New: " gprocida at google dot com
2023-03-22 12:29 ` [Bug default/30260] " gprocida at google dot com
2023-03-24 9:45 ` gprocida at google dot com
2023-10-24 15:24 ` dodji at redhat dot com
2023-10-24 15:43 ` woodard at redhat dot com
2023-11-30 16:35 ` dodji at redhat dot com
2023-11-30 21:51 ` gprocida at google dot com [this message]
2023-12-01 16:03 ` dodji at redhat dot com
2023-12-01 16:04 ` dodji 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-30260-9487-zxFRIn4LaC@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).