From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] pc bounds checking and namespaces
Date: Mon, 19 Jan 2004 19:18:00 -0000 [thread overview]
Message-ID: <yf2y8s3hhmp.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040119060642.DFA504B359@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Mon, 19 Jan 2004 01:06:42 -0500 (EST)")
On Mon, 19 Jan 2004 01:06:42 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:
> I'm about to add carlton_dictionary-branch and drow-cplus-branch to
> my test bed. That ought to help.
> Instead of finding these problems at the point of merging
> the branches onto HEAD, how about if we fix the branches so that
> they have zero regressions versus gdb 6.0, and then merge the
> branches?
In general, that's obviously a good idea. Having said that,
carlton_dictionary-branch is attempting a delicate enough task that I
suspect that, in some circumstances, we'll have to accept regressions.
It's trying to convert GDB from using the wrong names for things to
using the right names for things, and to do this whenever possible in
the presence of inadequate debug information; doing this while
simultaneously supporting the bugs and foibles of multiple versions of
GCC is a very hard task, and one which can adversely affect GDB's
maintainability.
But, at the very least, all regressions should be analyzed, so we can
figure out what's causing them, in what circumstances they will crop
up, and how easy they would be to fix.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-01-19 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 6:06 Michael Elizabeth Chastain
2004-01-19 18:16 ` Andrew Cagney
2004-01-19 19:18 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-17 0:49 David Carlton
2004-01-19 0:05 ` Elena Zannoni
2004-01-19 18:36 ` David Carlton
2004-01-22 19:57 ` 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=yf2y8s3hhmp.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ezannoni@redhat.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