On Thu, Apr 21, 2005 at 06:10:19PM -0700, Bryan Richter wrote: > I am working on porting GCC to the TI C54x.
Cool. > months, similar to others who have attempted this project, but I am now > in the process of setting up a repository on BerliOS so I can work with > others. Maybe not so cool, unless you are careful. The problem is that if you don't keep track of who submitted what, or if you accept some critical code from someone who is either unwilling or unable to legally contribute their work to the FSF, it can never be accepted as part of the official GCC. Please read http://gcc.gnu.org/contribute.html for requirements on contributing work to GCC, and http://gcc.gnu.org/contributewhy.html for why it's a good idea to go along. You're setting yourself up to build a separate, isolated group of developers, rather than working with the GCC experts, if you go off and start your own site and your own separate project. You can do that if you want, but it has disadvantages. At the least, you need to have your ducks in a row so that, when you are ready to talk about getting your port into GCC, if can be done (meaning that you've followed the standards and that all contributors are prepared to contribute their work). > 2. I plan on taking a GCC release (say, gcc-4.0.0-20050417), treating it > as a constant, and building the port on top of it. That way I won't have > to concern myself with the development of the rest of GCC (which would > hardly affect me). Is this the best method? No; the rest of GCC will affect you. If you ever want your work accepted as part of GCC, it has to work with the current development trunk. You're better off grabbing a snapshot of the trunk (what will become 4.1), working on that, and occasionally re-syncing to make sure that nothing has been broken. I don't think the revision control system you use matters, because if and when you are ready to contribute the port to GCC, the previous history is not going to be relevant, and all subsequent development would be inside GCC's revision control system (currently CVS, but likely to switch to subversion some time soon).
