From: David Carlton <carlton@math.stanford.edu>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: Namespace testcases
Date: Fri, 15 Nov 2002 15:37:00 -0000 [thread overview]
Message-ID: <ro1d6p6o156.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro1of8zangg.fsf@jackfruit.Stanford.EDU>
On 08 Nov 2002 11:08:47 -0800, David Carlton <carlton@math.Stanford.EDU> said:
> On Fri, 8 Nov 2002 13:34:35 -0500, Elena Zannoni <ezannoni@redhat.com> said:
>> What do you think of pushing the namespaces.exp additions to mainline
>> gdb? I would like to mark the failures with kfail and open
>> corresponding gnats PRs.
> That sounds reasonable to me. I've got several testcases involving
> namespace scope issues, anonymous namespaces, namespace aliases, and
> using declarations; I can post an RFA for them on the mainline as soon
> as there are PR's for them. I'll put adding PR's on my To Do list.
> Maybe Daniel could come up with some test cases/PR's involving the
> fact that GDB doesn't know what namespaces types are defined in.
I've filed PR's for everything that comes to mind. I probably missed
a few subtleties, but it's a start. Hopefully next week I'll be able
to find some time to clean up the testcases that I currently have on
the branch and file a mainline RFA for them.
>> So we can really know where we are....and have the satisfaction of
>> telling people reporting problems: "yeah, known bug, see PR/1234".
Not only can we tell people that, we can blame everything on GCC. :-)
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-11-15 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 10:38 Elena Zannoni
2002-11-08 11:09 ` David Carlton
2002-11-15 15:37 ` David Carlton [this message]
2002-11-15 17:23 ` Elena Zannoni
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=ro1d6p6o156.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.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