Dnia 06-04-2008, nie o godzinie 15:23 +0200, "Martin v. Löwis" pisze:
> What operating system and compiler? Does the behaviour change if you > compile without optimization? You are right, this is a gcc bug. Python built with OPT=-O0 passed to configure. This is Linux/athlon, gcc-4.3.0 snapshot from 2008-03-13. Since I recently encountered a particular gcc-4.3.0 bug, I confirmed that it is the cause here too: Python-3.0a4 builds with "-O3 -fwrapv -fno-tree-vrp" but hangs with "-O3 -fwrapv". The bug is already fixed in gcc: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35833 The bug is present in gcc-4.3.0 released a month ago, so someone with vanilla gcc-4.3.0 might check this. Adding -fno-tree-vrp is a workaround for gcc-4.3.0. -- __("< Marcin Kowalczyk \__/ [EMAIL PROTECTED] ^^ http://qrnik.knm.org.pl/~qrczak/ _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
