From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29360] New: Ada ranges emitting/reading/diffing are not supported in libabigail
Date: Tue, 12 Jul 2022 15:50:21 +0000 [thread overview]
Message-ID: <bug-29360-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29360
Bug ID: 29360
Summary: Ada ranges emitting/reading/diffing are not supported
in libabigail
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: ---
fedabipkgdiff --self-compare -a --from fc36 zlib-ada
Appears to be stuck. Upon closer look it appears that abipkgdiff is stuck in
an infinite loop:
build/tools/abipkgdiff --self-check --d1
/home/dodji/.cache/fedabipkgdiff/downloads/zlib-ada-debuginfo-1.4-0.30.20120830CVS.fc36.x86_64.rpm
/home/dodji/.cache/fedabipkgdiff/downloads/zlib-ada-1.4-0.30.20120830CVS.fc36.x86_64.rpm
.
Free form range types (range types that are not part of array types), used in
Ada are not fully supported by Libabigail.
What is not supported is their serilization in abixml, their de-serialization
from abixml and their comparison by the comparison engine.
I started a branch with that work, at
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/free-range-types.
What needs to be done is the support for diffing. Basically, creating a diff
type for range types, coming up with a compute_diff function that takes ranges
and returns the diff type for ranges and adding support for reporting the
changes carried by the range diff type.
This is a nice little feature to work on, IMHO.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-12 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 15:50 dodji at redhat dot com [this message]
2022-07-12 15:55 ` [Bug default/29360] " dodji at redhat dot com
2023-04-06 11:20 ` dodji at redhat dot com
2023-04-06 11:21 ` dodji at redhat dot com
2023-04-07 18:16 ` dodji at redhat dot com
2023-04-07 18:17 ` 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-29360-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).