From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@kealia.com, gdb-patches@sources.redhat.com, mec@shout.net
Cc: drow@mvista.com, kevinb@redhat.com
Subject: Re: [patch/testsuite] gdb.c++/classes.exp: add another ptype pattern
Date: Wed, 02 Jul 2003 21:33:00 -0000 [thread overview]
Message-ID: <200307022133.h62LXPPZ029851@duracef.shout.net> (raw)
Okay, here's my understanding:
. as of gcc 3.3, enums and classes which are nested in other classes now
have a stab name such as "ClassWithEnum::PrivEnum" rather than just
"PrivEnum".
. this is intentional
. this is a good thing -- drow mentioned it at one point and carlton
likes it too.
. as of gcc 3.3, enums and classes which are nested in namespaces
still have stab names such as "PrivEnum".
. there's still work to do in gdb.
. ... so it's hard to write a test case.
I'm going to leave inherit.exp alone and withdraw my patch. This will
leave the gcc 3.3 -gstabs+ case with a FAIL, which is okay. Someone will
pick it up again later when they get to the work in gdb.
I'm satisfied that the change from gcc 3.2.3 to gcc 3.3 is a good change.
So I can proceed down my list of "regressions with gcc 3.3 versus
gcc 3.2.3". When I get to the bottom of that list, I can drop test
coverage of gcc 3.2.3.
Michael C
next reply other threads:[~2003-07-02 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 21:33 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 20:58 Michael Elizabeth Chastain
2003-07-02 19:11 Michael Elizabeth Chastain
2003-07-02 17:28 Michael Elizabeth Chastain
2003-07-02 16:49 Michael Elizabeth Chastain
2003-07-02 17:07 ` David Carlton
2003-07-02 18:33 ` Daniel Jacobowitz
2003-07-02 19:02 ` Kevin Buettner
2003-07-02 19:19 ` David Carlton
2003-07-02 20:47 ` Kevin Buettner
2003-07-02 16:09 Michael Elizabeth Chastain
2003-07-02 16:29 ` David Carlton
2003-07-02 16:38 ` Daniel Jacobowitz
2003-07-02 16:01 Michael Elizabeth Chastain
2003-07-02 15:39 Michael Elizabeth Chastain
2003-07-02 15:51 ` Daniel Jacobowitz
2003-07-02 15:52 ` David Carlton
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=200307022133.h62LXPPZ029851@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.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