This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Two volunteers needed: New scheduler and aliasing code
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Subject: Re: Two volunteers needed: New scheduler and aliasing code
- From: Mark Mitchell <mmitchell at usa dot net>
- Date: Thu, 19 Mar 1998 17:03:48 GMT
- Cc: oliva at dcc dot unicamp dot br, gcc2 at cygnus dot com, egcs at cygnus dot com
- References: <9803191617.AA23881@vlsi1.ultra.nyu.edu>
- Reply-To: mmitchell at usa dot net
>>>>> "Richard" == Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
Richard> This would be much easier to do if GCC already had a
Richard> publicly-accessible anonymous CVS tree. In fact, I'd say
Richard> this would be very hard to do without CVS support.
My apologies for my mail software; I know that Kenner did not say the
above.
Richard> CVS is now being used for the GCC tree, but the system
Richard> administration folks at FSF are still waiting for
Richard> information about CVS in order to turn on anonymous
Richard> access.
I made this suggestion once before, but I'll try it again now that
Kenner and the FSF have moved forward with using CVS for GCC.
The merge work that Kenner has asked for, and that it was pointed out
above would be easier if there were public access to the CVS tree GCC2
sources, would be main even easier if GCC2 and EGCS shared a common
CVS tree. This is technically very feasible since CVS supports
branches. The branches are named, and there is no way that work on
one branch can affect another branch, unless an explict command to do
so is issued. A shared setup like that would make it much easier to
do merges back and forth, and to compute the differences between the
branches, thereby facilitating collaboration.
I believe that Jeff agreed at one point that Cygnus would be willing
to host the common tree, and provide access to Kenner and other FSF
maintainers.
--
Mark Mitchell mmitchell@usa.net
Stanford University http://www.stanford.edu