From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30309] self-compare reports differences on gcc-gnat from fc37
Date: Mon, 28 Aug 2023 15:38:22 +0000 [thread overview]
Message-ID: <bug-30309-9487-RPzU1gFHZC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30309-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30309
--- Comment #4 from dodji at redhat dot com ---
(In reply to dodji from comment #3)
> A candidate patch-set for this is being developed in a branch at
> https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/users/
> dodji/canonicalize-types-in-order.
>
> The branch is ready for testing and is being tested at the moment.
So, the branch "canonicalize-types-in-order" has been successfully tested using
libabigail-selfcheck against the packages defined for Fedora39 at
https://pagure.io/libabigail-selfcheck/blob/37b94a2689f11ddd240b204d25da6ca8549b5d9b/f/package-list.fedora39-base-non-reg.json.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-28 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 22:08 [Bug default/30309] New: gcc-gnat from fedora37 asserts woodard at redhat dot com
2023-04-03 22:09 ` [Bug default/30309] " woodard at redhat dot com
2023-04-07 18:23 ` [Bug default/30309] self-compare reports differences on gcc-gnat from fc37 dodji at redhat dot com
2023-04-07 18:23 ` dodji at redhat dot com
2023-04-07 18:24 ` dodji at redhat dot com
2023-05-18 21:18 ` woodard at redhat dot com
2023-08-28 10:55 ` dodji at redhat dot com
2023-08-28 15:38 ` dodji at redhat dot com [this message]
2023-08-28 15:56 ` 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-30309-9487-RPzU1gFHZC@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).