From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20202] New: Feature request: when printing substitute typedef for anoymous structure
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-20202-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=20202
Bug ID: 20202
Summary: Feature request: when printing substitute typedef for
anoymous structure
Product: libabigail
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
something like
typedef struct {
int member;
char member2;
} mystruct;
is enough of a C idiom that I think it would be a nice enahancement that
instead of printing something like:
[C]'function size_t _elf32_xltsize(const Elf_Data*, unsigned int, unsigned
int, int)' at 32.xlate\
tof.c:336:1 has some indirect sub-type changes:
parameter 1 of type 'const Elf_Data*' has sub-type changes:
in pointed to type 'const Elf_Data':
in unqualified underlying type 'typedef Elf_Data' at libelf.h:167:1:
underlying type 'struct __anonymous_struct__' at libelf.h:160:1
changed:
1 data member deletion:
'void* __anonymous_struct__::d_buf', at offset 0 (in bits) at
libelf.h:161:1
So instead of printing:
'void* __anonymous_struct__::d_buf', at offset 0 (in bits) at
libelf.h:161:1
Print something like:
'void* TheTypedefedName, at offset 0 (in bits) at libelf.h:161:1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-06-03 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 woodard at redhat dot com [this message]
2021-12-01 23:22 ` [Bug default/20202] " 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-20202-9487@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).