From: Keith Seitz <keiths@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] dwarf2_physname - cpexprs.exp
Date: Tue, 08 Dec 2009 21:27:00 -0000 [thread overview]
Message-ID: <4B1EC4A1.8050704@redhat.com> (raw)
In-Reply-To: <200911210520.45772.pedro@codesourcery.com>
On 11/20/2009 09:20 PM, Pedro Alves wrote:
> FAIL: gdb.cp/cpexprs.exp: print policyd4::policyd
> FAIL: gdb.cp/cpexprs.exp: print policyd<base, operation_1<base> >::policyd
> FAIL: gdb.cp/cpexprs.exp: list base::overload(base&) const
> FAIL: gdb.cp/cpexprs.exp: list base::overload(char*) const
> FAIL: gdb.cp/cpexprs.exp: list base::overload(int) const
> FAIL: gdb.cp/cpexprs.exp: list base::overload(long) const
> FAIL: gdb.cp/cpexprs.exp: list base::overload(short) const
> FAIL: gdb.cp/cpexprs.exp: list base::overload(void) const
> FAIL: gdb.cp/cpexprs.exp: list policyd4::policyd
> FAIL: gdb.cp/cpexprs.exp: list policyd<base, operation_1<base> >::policyd
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(base&) const
> FAIL: gdb.cp/cpexprs.exp: continue to base::overload(base&) const
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(char*) const
> FAIL: gdb.cp/cpexprs.exp: continue to base::overload(char*) const
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(int) const
> FAIL: gdb.cp/cpexprs.exp: continue to base::overload(int) const
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(long) const
> FAIL: gdb.cp/cpexprs.exp: continue to base::overload(long) const
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(short) const
> FAIL: gdb.cp/cpexprs.exp: continue to base::overload(short) const
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(void) const
> FAIL: gdb.cp/cpexprs.exp: continue to base::overload(void) const
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at policyd4::policyd
> FAIL: gdb.cp/cpexprs.exp: continue to policyd4::policyd
> FAIL: gdb.cp/cpexprs.exp: setting breakpoint at policyd<base, operation_1<base> >::policyd
> FAIL: gdb.cp/cpexprs.exp: continue to policyd<base, operation_1<base> >::policyd
>
> I've no idea if this is compiler badness or not. I haven't investigated.
With FSF GCC 4.2.4, the only failures I see are the policyd4-related
ones. I suspect that this might be caused by the valops.c assumption
that Daniel recently corrected (my bad):
2009-12-04 Daniel Jacobowitz <dan@codesourcery.com>
* valops.c (value_struct_elt_for_reference): Do not rely on
field order.
> I also saw 1 FAIL->PASS in classes.exp, 2 new PASS->FAILs and 2 new FAIL->PASSes
> in namespace.exp.
We've already established the namespace.exp status, so what remains is
the new PASS in classes.exp, which I'm guessing is not a problem. :-)
Keith
next prev parent reply other threads:[~2009-12-08 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:08 Keith Seitz
2009-11-21 5:21 ` Pedro Alves
2009-12-08 21:27 ` Keith Seitz [this message]
2009-11-21 17:12 ` Daniel Jacobowitz
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=4B1EC4A1.8050704@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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