From: "marcandre.lureau at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27715] Fails to detect GObjectClass ABI changes
Date: Thu, 29 Apr 2021 15:13:05 +0000 [thread overview]
Message-ID: <bug-27715-9487-LnVTc9n6Xf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27715-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27715
--- Comment #11 from Marc-André Lureau <marcandre.lureau at gmail dot com> ---
(In reply to Matthias Maennich from comment #9)
> [..]
> So, as much as I would also like to sometimes inspect underlying types of
> void*, flagging changes to those types is probably wrong. If you want this
> type to be stable, you need to let it participate as a type in the interface.
This bug is about structures that are exposed in the public header. So they may
be taken as argument, or returned, by void* or parent* pointers, but it would
be nice to annotate the actual type
> One way of achieving this is to define a symbol just for the sake of ABI
> analysis:
>
> void (struct _GTypeModuleClass obj) { }
>
> This will get picked up by libabigail and the type will participate in the
> analysis then.
Ok, but I am looking for a more friendly way to express that *all* my types in
my headers must be taken into account without having to define such extra
symbols. Imho it should be an option to the tool somehow.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-29 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 17:05 [Bug default/27715] New: " marcandre.lureau at gmail dot com
2021-04-09 17:54 ` [Bug default/27715] " maennich at android dot com
2021-04-12 8:21 ` marcandre.lureau at gmail dot com
2021-04-12 9:49 ` maennich at android dot com
2021-04-12 13:54 ` marcandre.lureau at gmail dot com
2021-04-12 13:55 ` marcandre.lureau at gmail dot com
2021-04-12 13:55 ` marcandre.lureau at gmail dot com
2021-04-12 14:05 ` maennich at android dot com
2021-04-12 19:01 ` marcandre.lureau at gmail dot com
2021-04-14 10:53 ` maennich at android dot com
2021-04-20 11:55 ` marcandre.lureau at gmail dot com
2021-04-29 15:13 ` marcandre.lureau at gmail dot com [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-27715-9487-LnVTc9n6Xf@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).