From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29691] mingw32-gcc-gfortran from f37 asserts during self-compare with 2.1
Date: Thu, 23 Mar 2023 17:20:06 +0000 [thread overview]
Message-ID: <bug-29691-9487-KjkyyNfFI9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29691-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29691
dodji at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from dodji at redhat dot com ---
This issue seems to be fixed in the recent master branch.
The tip of the branch is this commit:
a8a4ca88 abipkgdiff: Fix a typo
In other words, the issue should be fixed in the upcoming 2.3 release.
Thank you for reporting this problem and sorry for the inconvenience.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-03-23 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 21:30 [Bug default/29691] New: " woodard at redhat dot com
2022-10-14 21:30 ` [Bug default/29691] " woodard at redhat dot com
2023-03-22 17:13 ` dodji at redhat dot com
2023-03-23 17:20 ` dodji at redhat dot com [this message]
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-29691-9487-KjkyyNfFI9@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).