Hi Eirik,
the difference is very simple: all VACPP builds from IBM that have been
released so far have been compiled without any optimizations. The reason
for that is that once the optimizer is enabled, the binaries don't work
anymore. Clearly bugs with the 3.6.5 optimizer. In order to solve this,
IBM has to selectively enable all single optimizer features until they
find the one that generates bad code. So they have plenty of optimizations
left, just need to invest the time to find working settings.
Maybe someone from outside is willing to play with the /O* settings
of VACPP?
Also, gcc is supposed to have the better optimizer, especially pgcc
and egcs but they currenctly generate corrupt binaries, too.
Best regards,
Achim Hasenmueller
