[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

STINNER Victor added the comment: > Looks like code generation is borked. I sent an email to the mailing list: http://gcc.gnu.org/ml/gcc-help/2011-01/msg00136.html -- ___ Python tracker ___

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Antoine Pitrou added the comment: [...] > > gcc-4.6 -O1 -ftree-vectorize > - > 0x00480991 <+5041>: mov%eax,%ecx > 0x00480993 <+5043>: sub%edx,%ecx > 0x00480995 <+5045>: mov%ecx,(%r12,%rax,4) > 0x00480999 <+5049>:

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

STINNER Victor added the comment: More info about the loop: Py_ssize_t i; int nops; My setup: * Intel(R) Pentium(R) 4 CPU 3.00GHz * Debian Sid * gcc (Debian 20110106-1) 4.6.0 20110106 (experimental) [trunk revision 168538] -- ___ Python

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

STINNER Victor added the comment: With gcc-4.6 -O1, Python 3.2 works correctly. With gcc-4.6 -O1 -ftree-vectorize, the assertion "assert (new_line - last_line < 255);" fails in PyCode_Optimize(). I think that the problem is in the following loop: - #define

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Stefan Krah added the comment: I narrowed this issue down to -ftree-vectorize, which is part of -O3. -- ___ Python tracker ___ ___ Pyt

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Antoine Pitrou added the comment: You can look at Python/compile.c (the ast-to-bytecode compiler), Python/peephole.c (the bytecode optimizer), Python/marshal.c (the on-disk bytecode serializer/unserialize). First step could be to actually disable the optimizer (see PyCode_Optimize in peephol

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Tom Browder added the comment: I'm getting no interest from the gcc group at the moment. I would like to help track down the bug and will nose around the Python source to zero in on where the problem is for detailed debugging. Can anyone point me to the key files that concern the byte compi

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Tom Browder added the comment: Here is a link to the thread I started on the gcc-help mailing list concerning the issue: http://gcc.gnu.org/ml/gcc-help/2010-09/msg00170.html If I don't get a successful build with the current gcc trunk, I imagine this thread will transfer to the gcc (dev)

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Amaury Forgeot d'Arc added the comment: You're welcome. Please join a link to the gcc bug when you have one. -- resolution: -> invalid status: open -> pending ___ Python tracker ___

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Tom Browder added the comment: Correction on the bad gcc compiler: the actual version was a non-released version off the gcc-4.6 branch: gcc version 4.6.0 20100908 (experimental) (GCC). I'm filing a bug with gcc. Sorry for the wasted time. -- __

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Tom Browder added the comment: The build succeeded with the older version of gcc. I either have a mis-compiled gcc-4.5.1 (but the same version on another host worked okay) or gcc has a very subtle bug. I think this issue can be considered closed; however, it may be worth a note in a FAQ or

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Tom Browder added the comment: I'm using gcc-4.5.1. I'll try an older version: gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3. -- ___ Python tracker ___

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Amaury Forgeot d'Arc added the comment: For some reason your file os.pyc is corrupted: I loaded it with a working python2.7: import marshal, dis pyc = open('bados.pyc', 'rb').read() code = marshal.loads(pyc[8:]) dis.dis(code) And it appears that all the "jump" instructions are wrong: the addre

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Barry A. Warsaw added the comment: Note that I tried to reproduce this on my 10.04.1 system, with various states of Python 2.7 installed, etc. and was unable to reproduce it. It's certainly odd that you're getting the SystemError on that line. --

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Tom Browder added the comment: File attached as requested. -- Added file: http://bugs.python.org/file18905/os.pyc ___ Python tracker ___ _

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Amaury Forgeot d'Arc added the comment: Maybe a corrupted .pyc file? Can you please attach the file /usr/local/src/python-2.7-maint-svn/Lib/os.pyc -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

Changes by Tom Browder : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue9880] Python 2.7 Won't Build: SystemError: unknown opcode

New submission from Tom Browder : I am trying to rebuild the 2.7 maintenance branch and get this error on Ubuntu 10.04.1 LTS: XXX lineno: 743, opcode: 0 Traceback (most recent call last): File "/usr/local/src/python-2.7-maint-svn/Lib/site.py", line 62, in import os File "/usr/local/src/pyth