This is the mail archive of the
mailing list for the GCC project.
Re: GNU Pascal branch
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Adriaan van Os <gcc at microbizz dot nl>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 30 Mar 2006 11:25:29 -0500
- Subject: Re: GNU Pascal branch
- References: <email@example.com>
On 03/30/06 03:32, Adriaan van Os wrote:
> Still, I would like to create a GNU Pascal branch for gcc. This will be
> a central place where to keep the compiler updated with
I don't think this is a good idea. You are either part of the compiler
or you aren't. Front ends that are only partially incorporated will
naturally suffer bit-rot and be largely ignored. Even if the FE is not
enabled by default, you can benefit from being integrated in the rest of
the compiler (e.g., Ada).
If you were to integrate the gpc FE with the rest of the compiler, then
you would only need to worry about FE bugs. The ME and BE bugs exposed
by your front end would then be treated as first class citizens in our
> <http://gcc.gnu.org/svnwrite.html#branches> explains how to create a
> branch, so I am looking for a gcc maintainer to approve for write access
> (solely for the branch). I signed an FSF assignment for the GNU Pascal
> compiler on February 15, 2005 (OS/RT 220644).
If you have an FSF assignment then it's only a matter of filling in the
SVN access form. You can use my address as reference in the form. Then
it's just a matter of posting the back-end and front-end patches to
If the BE patches are not specific to gpc and fix bugs reproducible with
other FEs, we could even consider adding them to mainline.
But first, you have to decide whether you want to integrate with the
rest of the compiler or not. Halfway integration will be a waste of