From: Daniel Jacobowitz <dan@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [commit] Delay reading of struct members
Date: Thu, 09 Sep 2010 13:14:00 -0000 [thread overview]
Message-ID: <20100908234233.GW28036@caradoc.them.org> (raw)
In-Reply-To: <20100908192459.GH28036@caradoc.them.org>
On Wed, Sep 08, 2010 at 03:24:59PM -0400, Daniel Jacobowitz wrote:
> I've tested this on x86_64-linux and arm-eabi, using GCC 4.4, GCC 4.5,
> and RealView; I also tested it on hand-modified GCC output to trigger
> the template argument support. No regressions; committed to HEAD.
At the last minute I broke the test for RealView; just a cosmetic
difference (something GCC doesn't support, but should).
--
Daniel Jacobowitz
CodeSourcery
2010-09-08 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.cp/templates.exp (test_template_args): Allow "struct".
Index: gdb.cp/templates.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.cp/templates.exp,v
retrieving revision 1.27
diff -u -p -r1.27 templates.exp
--- gdb.cp/templates.exp 8 Sep 2010 19:09:43 -0000 1.27
+++ gdb.cp/templates.exp 8 Sep 2010 23:41:09 -0000
@@ -200,10 +200,10 @@ proc test_template_args {} {
set empty_re "Empty *<void *\\(FunctionArg *<int>\\)>"
gdb_test "ptype empty" \
- "type = class $empty_re {.*<no data fields>.*}"
+ "type = (struct|class) $empty_re {.*<no data fields>.*}"
gdb_test "ptype arg" \
- "type = class FunctionArg<int> {.*int method\\($empty_re \\&\\);.*}"
+ "type = (struct|class) FunctionArg<int> {.*int method\\($empty_re \\&\\);.*}"
}
proc do_tests {} {
next prev parent reply other threads:[~2010-09-08 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 20:39 Daniel Jacobowitz
2010-09-09 13:14 ` Daniel Jacobowitz [this message]
2010-09-09 20:36 ` Tom Tromey
2010-09-09 23:32 ` Daniel Jacobowitz
2010-09-10 12:18 ` Tom Tromey
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=20100908234233.GW28036@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@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