Dear Chief,
Is there anyone else out there?
I can hire a computer science student for the summer to work on GPC, but I don't think they will be capable of doing much with the migration to newer versions of GCC. They may be able to help with other projects.
It seems to me that the compiler is complete wrt ISO Standard Pascal.
I have no complaints.
Some have referred to gaps in EP compliance (are these gaps deal breakers?). It might be helpful to have a complete list, with simple example code that should compile.
Enhancing the compiler is something a CS student could attempt.
Unless the compiler itself is going to be improved by any remaining fixing bugs and implementing the missing features, what would be the point of simply chasing gcc releases (a hairy and never-ending task)?
If we can be sure of compiling GCC 3.4.6 on Windows, Linux, and MacOS using whatever version of GCC is current for those platforms, then I think we should be okay. I'm confident we can do so on Windows 32-bit, Linux 32-bit and Linux 64-bit. I can't compile GCC 3.4.6 on Windows 64-bit I believe because of divergeance between MinGW 64-bit and MinGW 32-bit. On MacOS I can't compile GCC 3.4.6. It took me some time to get GPC to run on MacOS 10.7.5, but I just posted my notes on how to do that.
http://alignment.hep.brandeis.edu/Software/Pascal/Pascal.html#Notes
We (my group) is going to try to get the same MacOS GPC binaries working on MacOS 10.9 and later.
Mac OSX seems to have major issues here, but it is probably nothing that cannot be solved by; [a] suitably amending the gpc driver program (gpc.c) to pass on any needed arguments, or [b] by writing a custom collect2.c to replace the default collect2.c, and compiling it separately, or [c] by writing your own os-hacks.h and putting in the include directory.
Okay. We will look into that here.
If anyone is interested, I have samples of [a], [b] and [c]
I have your os-hacks.h file. Is there more? If so, then yes I'm interested.
Yours, Kevan