From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28675] whitespace in DWARF template naming confuses libabigail.
Date: Thu, 09 Dec 2021 00:10:28 +0000 [thread overview]
Message-ID: <bug-28675-9487-HKxpfz1wKH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28675-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28675
--- Comment #1 from Ben Woodard <woodard at redhat dot com> ---
This may be a duplicate of 28664 depending on how you frame it. In 28664 it has
to do with the template value parameter type. In this case it is the
representation of certain template type parameter.
One way of considering the bugs is that both have to do with string comparison
of the template typename vs. drilling down into the types being instantiated by
the template. In that case they may be the same bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-12-09 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 23:44 [Bug default/28675] New: " woodard at redhat dot com
2021-12-08 23:44 ` [Bug default/28675] " woodard at redhat dot com
2021-12-09 0:10 ` woodard 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-28675-9487-HKxpfz1wKH@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).