public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@redhat.com>
To: libabigail@sourceware.org
Cc: dodji@redhat.com, woodard@redhat.com
Subject: [PATCH 0/2] Fix array subrange (de) serialization
Date: Fri, 27 Nov 2020 17:30:21 +0100	[thread overview]
Message-ID: <87wny67of6.fsf@redhat.com> (raw)

Hello,

The following two small patches are to fix bug
https://sourceware.org/bugzilla/show_bug.cgi?id=26780 where libabigail
fails to properly serialise Fortran array sub-ranges.

The first patch is just a small cleanup patch for a little issue I saw
while looking at the bug.  The second patch is the bug fix itself.

The two patches have been applied to master.

Dodji Seketeli (2):
  reader: Read array subrange length into an uint64_t
  Bug 26780 - Fix array subrange bounds (de)serialization

 src/abg-reader.cc                             |  28 ++++++++++++++++--
 src/abg-writer.cc                             |  10 +++++++
 tests/data/Makefile.am                        |   3 ++
 .../hdf5-1.10.6-2.fc33.x86_64.rpm             | Bin 0 -> 2227815 bytes
 ...10.6-2.fc33.x86_64.self-check-report-0.txt |  24 +++++++++++++++
 .../hdf5-debuginfo-1.10.6-2.fc33.x86_64.rpm   | Bin 0 -> 3825438 bytes
 tests/test-diff-pkg.cc                        |  12 ++++++++
 7 files changed, 75 insertions(+), 2 deletions(-)
 create mode 100644 tests/data/test-diff-pkg/hdf5-1.10.6-2.fc33.x86_64.rpm
 create mode 100644 tests/data/test-diff-pkg/hdf5-1.10.6-2.fc33.x86_64.self-check-report-0.txt
 create mode 100644 tests/data/test-diff-pkg/hdf5-debuginfo-1.10.6-2.fc33.x86_64.rpm

-- 
2.29.2

-- 
		Dodji


             reply	other threads:[~2020-11-27 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 16:30 Dodji Seketeli [this message]
2020-11-27 16:39 ` [PATCH 1/2] reader: Read array subrange length into an uint64_t Dodji Seketeli
2020-11-27 16:40 ` [PATCH 2/2] Bug 26780 - Fix array subrange bounds (de)serialization Dodji Seketeli

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=87wny67of6.fsf@redhat.com \
    --to=dodji@redhat.com \
    --cc=libabigail@sourceware.org \
    --cc=woodard@redhat.com \
    /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).