From: Mike Stump <mikestump@comcast.net>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [debug-early] handle objects containing variable-length members
Date: Sat, 11 Apr 2015 05:07:00 -0000 [thread overview]
Message-ID: <566427DE-5A4C-416D-BBE6-01EEEFD5DD02@comcast.net> (raw)
In-Reply-To: <55281589.9010209@redhat.com>
On Apr 10, 2015, at 11:25 AM, Aldy Hernandez <aldyh@redhat.com> wrote:
> < KFAIL: gdb.cp/oranking.exp: p foo4(&a) (PRMS: gdb/12098)
> ---
> > KPASS: gdb.cp/oranking.exp: p foo4(&a) (PRMS gdb/12098)
> 20065c20065
> < KFAIL: gdb.cp/oranking.exp: p foo101("abc") (PRMS: gdb/12098)
> ---
> > KPASS: gdb.cp/oranking.exp: p foo101("abc") (PRMS gdb/12098)
> 28222c28222
>
> Plus some noise regarding threads.
>
> I don't know what KFAIL/KPASS are, having lived in GCC land too long, but I will take a look at those next.
Known pass, known fail. These are tied to the named PR in the gdb database. As they are fixed, likely those bugs should be updated to reflect the improvement in gcc, but see the gdb folks for how to do that.
prev parent reply other threads:[~2015-04-11 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 18:25 Aldy Hernandez
2015-04-11 5:07 ` Mike Stump [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=566427DE-5A4C-416D-BBE6-01EEEFD5DD02@comcast.net \
--to=mikestump@comcast.net \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.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).