From: Keith Seitz <keiths@redhat.com>
To: Sandra Loosemore <sandra@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [committed, testsuite] Reapply fix for gdb.cp/var-tag.exp C++ failures
Date: Thu, 30 Jul 2015 20:56:00 -0000 [thread overview]
Message-ID: <55BA8F8C.8080301@redhat.com> (raw)
In-Reply-To: <55BA74C2.8050800@codesourcery.com>
On 07/30/2015 12:02 PM, Sandra Loosemore wrote:
> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E
> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype ee
> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype EE
> FAIL: gdb.cp/var-tag.exp: before start: c++: ptype E2
> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E
> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype ee
> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype EE
> FAIL: gdb.cp/var-tag.exp: in main: c++: ptype E2
> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype E
> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype ee
> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype EE
> FAIL: gdb.cp/var-tag.exp: in C::f: c++: ptype E2
Yeah, GCC5 is now outputting (into DWARF) the underlying types used to
implement the enum. I had a patch lying around, but I forgot about it.
Thank you for doing this.
> diff --git a/gdb/testsuite/gdb.cp/var-tag.exp b/gdb/testsuite/gdb.cp/var-tag.exp
> index 30aab99..60379e9 100644
> --- a/gdb/testsuite/gdb.cp/var-tag.exp
> +++ b/gdb/testsuite/gdb.cp/var-tag.exp
> @@ -28,13 +28,18 @@ if {[prepare_for_testing $testfile.exp $testfile \
>
> proc do_global_tests {lang} {
> set invalid_print "Attempt to use a type name as an expression"
> - set ptypefmt "type = (class|enum|union|struct) %s {.*}"
> +
> + if {$lang == "c++"} {
> + set opt_underlying "(: unsigned int )?"
> + } else {
> + set opt_underlying ""
Missing '}' ?
> + set ptypefmt "type = (class|enum|union|struct) %s $opt_underlying{.*}"
Keith
next prev parent reply other threads:[~2015-07-30 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 19:04 Sandra Loosemore
2015-07-30 20:56 ` Keith Seitz [this message]
2015-07-30 21:26 ` Sandra Loosemore
2015-07-30 21:32 ` Keith Seitz
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=55BA8F8C.8080301@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@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