From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27970] instability in canonicalization causes libstdc++ to fail selfcheck
Date: Tue, 21 Sep 2021 19:35:34 +0000 [thread overview]
Message-ID: <bug-27970-9487-v6JuXZEcAi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27970-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27970
--- Comment #4 from Ben Woodard <woodard at redhat dot com> ---
With the latest trunk as of 1115e3f08e8f30e7e412294a563a78a15d0373c1 this
continues to be a problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-21 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 20:43 [Bug default/27970] New: " woodard at redhat dot com
2021-06-08 20:44 ` [Bug default/27970] " woodard at redhat dot com
2021-09-07 17:46 ` woodard at redhat dot com
2021-09-08 15:02 ` woodard at redhat dot com
2021-09-21 19:35 ` woodard at redhat dot com [this message]
2021-09-22 15:21 ` dodji at redhat dot com
2021-09-22 15:22 ` [Bug default/27970] Duplicated member functions cause spurious self comparison changes dodji at redhat dot com
2021-09-23 11: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-27970-9487-v6JuXZEcAi@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).