From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30334] New: Support DW_TAG_iterface_type DIEs (for languages like D and Java)
Date: Tue, 11 Apr 2023 15:38:24 +0000 [thread overview]
Message-ID: <bug-30334-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30334
Bug ID: 30334
Summary: Support DW_TAG_iterface_type DIEs (for languages like
D and Java)
Product: libabigail
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
The D language as well as the Java language support "interface" types.
These can be generally implemented using the DW_TAG_interface_type DIE.
Libabigail currently doesn't support this DIE.
It could support it by constructing an abigail::ir::class_decl type, with a
abigail::ir::class_decl::is_interface() accessor that returns true if the class
is an interface.
That interface would thus allow only abstract member functions and constant
data members.
Here is what the DWARF 5 spec says:
5.7.2 Interface Type Entries
The Java language defines “interface” types. An interface in Java is similar to
a C++ or Java class with only abstract methods and constant data members.
Interface types are represented by debugging information entries with the tag
DW_TAG_interface_type.
An interface type entry has a DW_AT_name attribute, whose value is a
null-terminated string containing the type name.
[...]
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-04-11 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 15:38 dodji at redhat dot com [this message]
2023-04-11 15:40 ` [Bug default/30334] " dodji at redhat dot com
2023-04-11 15:41 ` 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-30334-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).