From: "gprocida+abigail at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26739] Handle qualified typedef array types
Date: Fri, 04 Dec 2020 17:09:49 +0000 [thread overview]
Message-ID: <bug-26739-9487-cxjWzgE0W5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26739-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26739
Giuliano Procida <gprocida+abigail at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NOTABUG |---
--- Comment #5 from Giuliano Procida <gprocida+abigail at google dot com> ---
Hi Dodji.
Please take a look at
https://sourceware.org/pipermail/libabigail/2020q4/002992.html. I used GCC
10.2.0.
This is actually a test case I came up with to exercise BTF (pahole / libbtf).
This is an area where, until we check and verify otherwise, no part of the
toolchain should be beyond suspicion.
However, we are definitely seeing some incorrect reporting here.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-12-04 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 18:21 [Bug default/26739] New: " gprocida+abigail at google dot com
2020-10-23 16:36 ` [Bug default/26739] " dodji at redhat dot com
2020-10-27 17:22 ` dodji at redhat dot com
2020-11-09 14:35 ` dodji at redhat dot com
2020-11-09 14:35 ` dodji at redhat dot com
2020-11-13 17:10 ` dodji at redhat dot com
2020-12-04 17:09 ` gprocida+abigail at google 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-26739-9487-cxjWzgE0W5@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).