This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

GNU Pascal branch


The GNU Pasal compiler <http://www.gnu-pascal.de> is maintained as a separate back-end project. The compiler can be built with gcc-2.8.1 up to gcc-3.4.x and preliminary support for gcc-4.0 was recently added (<http://www.gnu-pascal.de/crystal/gpc/en/thread13456.html>). A regular question is why gpc isn't integrated into the gcc repository. The answer is that simply the resources fail to maintain gpc on a daily basis on gcc mainline. Also, flexibility in choosing the back-end version sometimes has its advantages, dependent on the platform, given the fact that reported gcc bugs are not always fixed.

Apropos, <http://gcc.gnu.org/backends.html> seems to be pointing to the wrong page now.

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

* recent gpc snapshots
* patches to the front-end, posted on the GNU Pascal mailing list <http://www.gnu-pascal.de/crystal/gpc/en/> (to add features or to fix bugs)
* patches to the back-end and middle-end, needed to get things working for various targets.


<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).

Sincerely,

Adriaan van Os
<http://www.microbizz.nl/gpc.html>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]