Re: [pypy-dev] A bug in cc?
Hi Elmo, On Tue, Jul 25, 2006 at 01:01:23AM +0300, Elmo M?ntynen wrote: I have 4.0.4 (debian 4.0.3-4). How should we go about testing on the latest gcc, or are you doing it right now. I can definitely reproduce the bug with the that certain file(s). Which of the .gcda and .gcno (or the rest) files should I send? I don't know what these files are, so I can't comment, but you should look or ask around in the gcc community instead. Also, I'm sure they would like to see information related to their latest release, so you should try with that. And of course you should try to see if it's a known bug, maybe even if it's been fixed already... A bientot, Armin ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Re: [pypy-dev] A bug in cc?
Armin Rigo wrote: In any case, if the bug is still there in the latest gcc, yes, I'd consider reporting it. PyPy is good to push many limits of its backends -- e.g. it gave quite a few LLVM bug reports and I wouldn't be surpized if mono was next :-) mono *will be* the next, definitively :-). ciao Anto ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Re: [pypy-dev] A bug in cc?
Armin Rigo wrote: Hi Elmo, On Sun, Jul 23, 2006 at 09:43:05PM +0300, Elmo M?ntynen wrote: Now I got an internal compiler error from cc: Couldn't reproduce it... I ran python translate.py --backend=c --profopt='-c from richards import *;main(iterations=1)' --text --batch targetpypystandalone.py but everything went fine. It's a gcc 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9). Either it's a bug in a specific gcc version, or else maybe (just guessing) the floating-point exception is when gcc computes something with the profile data, maybe timings, in which case the bug could be hard to reproduce on a different machine. In any case, if the bug is still there in the latest gcc, yes, I'd consider reporting it. PyPy is good to push many limits of its backends -- e.g. it gave quite a few LLVM bug reports and I wouldn't be surpized if mono was next :-) A bientot, Armin I have 4.0.4 (debian 4.0.3-4). How should we go about testing on the latest gcc, or are you doing it right now. I can definitely reproduce the bug with the that certain file(s). Which of the .gcda and .gcno (or the rest) files should I send? Elmo ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Re: [pypy-dev] A bug in cc? (was: translation with --profopt fails)
Elmo Mäntynen wrote: Elmo Mäntynen wrote: Armin Rigo wrote: Hi Elmo, On Wed, Jul 19, 2006 at 04:11:58PM +0300, Elmo M??ntynen wrote: Last lines of output (python translate.py --backend=c --profopt='-c from richards import *;main(iterations=1)' --text --batch targetpypystandalone.py): I have no clue how --profopt can affect the translation itself. You don't get the same error without the --profopt option? A bientot, Armin Should've tested that, will do as soon as possible. benchmark.html on snake shows something that says to me that the profopt executable doesn't exist, which suggests that it wasn't built. Elmo Translation without profopt worked now, though there might have been something that got changed in between, will report after some more builds. Now I got an internal compiler error from cc: [cbuild:profopt] Gathering profile data from: /tmp/usession-11/testing_1/testing_1 -c from richards import *;main(iterations=1) [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c testing_1.c -o testing_1.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c structimpl.c -o structimpl.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes.c -o nonfuncnodes.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_1.c -o nonfuncnodes_1.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_2.c -o nonfuncnodes_2.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_3.c -o nonfuncnodes_3.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_4.c -o nonfuncnodes_4.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_5.c -o nonfuncnodes_5.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_6.c -o nonfuncnodes_6.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_7.c -o nonfuncnodes_7.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_8.c -o nonfuncnodes_8.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_9.c -o nonfuncnodes_9.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_10.c -o nonfuncnodes_10.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_11.c -o nonfuncnodes_11.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_12.c -o nonfuncnodes_12.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_13.c -o nonfuncnodes_13.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_14.c -o nonfuncnodes_14.o [cbuild:execute] cc -O2 -pthread -fprofile-use -I/home/drayko/Workfolder/Security/Python/cvs/pypy-dist/pypy/translator/c -I/usr/include/python2.4 -I/tmp/usession-11/testing_1 -c nonfuncnodes_15.c -o nonfuncnodes_15.o [cbuild:execute] cc -O2 -pthread -fprofile-use
Re: [pypy-dev] A bug in cc?
Elmo Mäntynen wrote: Elmo Mäntynen wrote: Elmo Mäntynen wrote: Armin Rigo wrote: Hi Elmo, On Wed, Jul 19, 2006 at 04:11:58PM +0300, Elmo M??ntynen wrote: Last lines of output (python translate.py --backend=c --profopt='-c from richards import *;main(iterations=1)' --text --batch targetpypystandalone.py): I have no clue how --profopt can affect the translation itself. You don't get the same error without the --profopt option? A bientot, Armin Should've tested that, will do as soon as possible. benchmark.html on snake shows something that says to me that the profopt executable doesn't exist, which suggests that it wasn't built. Elmo Translation without profopt worked now, though there might have been something that got changed in between, will report after some more builds. Now I got an internal compiler error from cc: [cbuild:profopt] Gathering profile data from: /tmp/usession-11/testing_1/testing_1 -c from richards import *;main(iterations=1) ... [translation:ERROR] File /usr/lib/python2.4/distutils/unixccompiler.py, line 115, in _compile [translation:ERROR] raise CompileError, msg [translation:ERROR] CompileError: command 'cc' failed with exit status 1 If this really calls for a bugreport, it would be better if some one more comfortable with the compiling process and the gcc toolset would do it. Should I send some of the produced files? Just to note that building without profopt works (this time its the same rev). Elmo ___ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
