As we speak, I am running the KenCC (Plan9 C compiler, ancestor of the Golang compiler) for the pts/compilation suite
CC=/opt/plan9/bin/pcc CXX=$CC (to avoid another c++ compiler to give results, looking at cfront to get results here... but I have not found a wrapper like fort77 for cfront)
I don't really understand you: what compilers did you use in the end? Why would you need a fortran wrapper to compile mplayer and the kernel?
My idea was to get a big fortran code and compile it with gfortran and co. Am I missing something?
No the only reason Fortran was discussed was because when PTS got upgraded, the compiler suite benchmarks required not only a C compiler but also a Fortran compiler.
To make "fair" comparison between compilers that do compile fortran (like GCC, open64) and those that do not, those that do not get the fort77 wrapper.
For mplayer and the kernel, that should not have any influence.
Unfortunately all these odd compilers fail the vast majority of the tests. I have not had time to play much with it lately though. The stuff is out there however so if someone wants to have a go at it, it is there
I would especially be interested to know if someone is able to run PTS tests on openwatcom. This is a weird piece of compiler that I do not really know how to use properly