[pypy-dev] gcc warnings / errors in translation

[Matti Picus]

warning: the stdio output of a translate is a very large webpage.

I wondered why the jit-benchmark-linux-x86-64 tests were failing to 
translate, where the pypy-c-jit-linux-x86-64 passed

for instance the failed build on tannit64
http://buildbot.pypy.org/builders/jit-benchmark-linux-x86-64/builds/581/steps/translate/logs/stdio
versus the successful build on allegro64
http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/1257/steps/translate/logs/stdio

Two things struck me from the failure of the make command:
- Could the difference be environmental gcc flags making warnings into 
errors on tannit64?
- There are alot of warnings, some of them seem important.
In looking back into history, we seem to have gotten worse with warnings.
I went back a bit, say to one of the release-2.0-beta1 builds, there are 
still tons of gcc warnings, but fewer
http://buildbot.pypy.org/builders/pypy-c-jit-linux-x86-64/builds/1115/steps/translate/logs/stdio

Anyone feel like taking a look?
Matti