From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: drow@false.org, gdb@sources.redhat.com,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Subject: Re: Branch created for inter-compilation-unit references
Date: Wed, 25 Feb 2004 16:10:00 -0000 [thread overview]
Message-ID: <1C4B9E16-67AD-11D8-9146-000A95DA505C@dberlin.org> (raw)
In-Reply-To: <403C2E96.8050409@gnu.org>
On Feb 25, 2004, at 12:11 AM, Andrew Cagney wrote:
>>> Merging the branch may have to wait until after GDB 6.1.
>> This process is looking like gcc, which is probably an improvement.
>> Develop on the branch; verify no regressions; then merge.
>
> Careful, GCC is currently faceing an SSA mega-merge.
Um, except again, we are verifying no regressions in test results, plus
no serious (>5%) regressions in compile time or execution time.
You also forgot that the code has already been reviewed by global
maintainers who were working on the branch, and will again be design
reviewed before committing to the main branch.
Plus it includes both high-level design, and user-level documentation
Finally, the merge in question, plus the document describing the merge
and it's criteria, was explicitly approved by the GCC Steering
Committee.
> A strategy, reminiscent of the HP merge, is not one we want to
> encourage here.
The HP merge was completely different than the above.
It seems like you are trying to degrade gcc here by comparing the SSA
merge to the HP merge, which is clearly a dumb comparison.
Just because certain gdb people screwed that merge up by not requiring
more doesn't mean GCC will do the same, as evidenced by the above.
> Haveing said that short lived branches for experimentation are a good
> idea.
>
> Andrew
>
>
next prev parent reply other threads:[~2004-02-25 16:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 3:51 Michael Elizabeth Chastain
2004-02-25 5:12 ` Andrew Cagney
2004-02-25 16:10 ` Daniel Berlin [this message]
2004-02-25 17:01 ` Andrew Cagney
2004-02-25 17:07 ` Daniel Berlin
2004-02-25 18:50 ` Andrew Cagney
2004-02-25 18:53 ` Daniel Berlin
2004-02-25 19:48 ` Andrew Cagney
2004-02-26 5:48 ` Eli Zaretskii
2004-02-26 6:06 ` Daniel Berlin
2004-02-26 6:31 ` Eli Zaretskii
2004-02-26 15:05 ` Daniel Jacobowitz
2004-02-26 16:19 ` Elena Zannoni
2004-02-26 16:25 ` Daniel Jacobowitz
2004-02-26 16:36 ` Elena Zannoni
2004-02-26 16:54 ` Daniel Jacobowitz
2004-02-26 19:01 ` Eli Zaretskii
2004-02-26 19:10 ` Eli Zaretskii
2004-02-26 19:24 ` Andrew Cagney
2004-02-26 19:28 ` Daniel Jacobowitz
2004-02-26 20:19 ` Andrew Cagney
2004-02-26 5:48 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2004-02-21 20:08 Daniel Jacobowitz
2004-02-25 0:18 ` Daniel Jacobowitz
2004-02-25 0:35 ` Andrew Cagney
2004-02-25 1:29 ` Daniel Jacobowitz
2004-02-25 2:23 ` Andrew Cagney
2004-02-25 2:27 ` Daniel Jacobowitz
2004-02-25 3:17 ` Andrew Cagney
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=1C4B9E16-67AD-11D8-9146-000A95DA505C@dberlin.org \
--to=dberlin@dberlin.org \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@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