From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [cplus] An initial use of the canonicalizer
Date: Wed, 31 Dec 2003 00:59:00 -0000 [thread overview]
Message-ID: <20031231005909.GA19866@nevyn.them.org> (raw)
In-Reply-To: <20031230211502.E56374B35A@berman.michael-chastain.com>
On Tue, Dec 30, 2003 at 04:15:02PM -0500, Michael Chastain wrote:
> Uh, I don't like parts of this.
That's why I'm not submitting it for mainline yet. Sorry if I wasn't
clear. The [cplus] tag means it's going on my branch.
>
> - -re "type = (class |)Foo<volatile char ?\\*> \\{\r\n\[ \t\]*public:\r\n\[ \t\]*int x;\r\n\[ \t\]*.*char.*\\*t;\r\n\r\n\[ \t\]*.*char.* \\* foo\\(int,.*char.*\\*\\);\r\n\\}\r\n$gdb_prompt $" { pass "ptype fvpchar" }
> + -re "type = (class |)Foo<.*char.* ?\\*> \\{\r\n\[ \t\]*public:\r\n\[ \t\]*int x;\r\n\[ \t\]*.*char.*\\*t;\r\n\r\n\[ \t\]*.*char.* \\* foo\\(int,.*char.*\\*\\);\r\n\\}\r\n$gdb_prompt $" { pass "ptype fvpchar" }
>
> You dropped the "volatile" from the expected test pattern.
> Can you do something like:
>
> (volatile char ?*|char volatile ?*)
What's going to happen in the end is that we won't need any of this
garbage. You'll be able to say:
char volatile\\*
and no matter what debug info format or compiler generated the object,
that's what GDB will print. For now I'm just kludging around things so
that I can see when I introduce regressions on my branch.
> Here is why: sometimes, I need to run the current test suite with gdb 6.0,
> because the 6.0 test suite no longer works with the current compiler.
> So it helps me a lot if the current test suite accepts the output
> of both gdb 6.0 and gdb HEAD.
>
> Sometimes this is painful but in cases like this it's easy and cheap.
Not when I'm done with my project, it won't be. Let's talk about the
problem. Which is more important - checking GDB 6.0 against GCC HEAD,
or being able to verify that I've successfully canonicalized _all_ of
GDB's output patterns?
I'd like to consider "volatile char *" a bug when we're expecting to
see "char volatile*", not accept both. As a general issue. (I
personally consider the former more natural, but the latter seems to be
more common C++ style and matches the demangler, for this specific
example).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-31 0:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 21:15 Michael Elizabeth Chastain
2003-12-31 0:59 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-31 19:04 Michael Elizabeth Chastain
2004-01-01 6:03 ` Eli Zaretskii
2004-01-01 7:50 ` Daniel Jacobowitz
2003-12-31 4:12 Michael Elizabeth Chastain
2003-12-31 14:04 ` Daniel Jacobowitz
2003-12-31 2:26 Michael Elizabeth Chastain
2003-12-31 3:36 ` Daniel Jacobowitz
2003-12-31 1:43 Michael Elizabeth Chastain
2003-12-31 2:09 ` Daniel Jacobowitz
2003-12-30 21:03 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=20031231005909.GA19866@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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