Hello.
I've been notified that many of the Python interpreters started to fail with new GNU Toolchain (gcc 11, glibc 2.33).
https://koschei.fedoraproject.org/package/pythonX.Y (replace X.Y with version)
Python 3.5 - test_buffer fails on aarch64 - test_buffer+test_dbm_gnu fails on ppc64le - %check segafults on x86_64
Python 3.6 - %check segafults on x86_64 - test_buffer fails on aarch64
Python 3.7 - test_buffer fails on aarch64+ppc64le
Python 3.8 - seems to build fine
Python 3.9 - test_buffer fails on aarch64+ppc64le
Python 3.10 - seems to build fine
PyPys have not yet been collected by Koschei, Python 2.7 seems fine.
Oh, GCC 11 already landed on the Fedora Python buildbots running Rawhide. I created an issue to track the bugs on Python upstream:
test_buffer fails on Python built with GCC 11 https://bugs.python.org/issue42587
Victor
On Mon, Dec 7, 2020 at 1:26 PM Miro Hrončok mhroncok@redhat.com wrote:
Hello.
I've been notified that many of the Python interpreters started to fail with new GNU Toolchain (gcc 11, glibc 2.33).
https://koschei.fedoraproject.org/package/pythonX.Y (replace X.Y with version)
Python 3.5
- test_buffer fails on aarch64
- test_buffer+test_dbm_gnu fails on ppc64le
- %check segafults on x86_64
Python 3.6
- %check segafults on x86_64
- test_buffer fails on aarch64
Python 3.7
- test_buffer fails on aarch64+ppc64le
Python 3.8
- seems to build fine
Python 3.9
- test_buffer fails on aarch64+ppc64le
Python 3.10
- seems to build fine
PyPys have not yet been collected by Koschei, Python 2.7 seems fine.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
On Mon, Dec 7, 2020 at 4:08 PM Victor Stinner vstinner@redhat.com wrote:
Oh, GCC 11 already landed on the Fedora Python buildbots running Rawhide. I created an issue to track the bugs on Python upstream:
test_buffer fails on Python built with GCC 11 https://bugs.python.org/issue42587
I bisected the code from 500K lines of C code (CPython) to a short reproducer (44 lines, unrelated to Python) and I reported the issue to GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98190
GCC got a fix: https://gcc.gnu.org/g:3e60ddeb8220ed388819bb3f14e8caa9309fd3c2
What is the next step to get the GCC fix in Fedora?
Victor
Hi Victor.
On 12/14/20 11:23 AM, Victor Stinner wrote:
On Mon, Dec 7, 2020 at 4:08 PM Victor Stinner vstinner@redhat.com wrote:
Oh, GCC 11 already landed on the Fedora Python buildbots running Rawhide. I created an issue to track the bugs on Python upstream:
test_buffer fails on Python built with GCC 11 https://bugs.python.org/issue42587
I bisected the code from 500K lines of C code (CPython) to a short reproducer (44 lines, unrelated to Python) and I reported the issue to GCC: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98190
GCC got a fix: https://gcc.gnu.org/g:3e60ddeb8220ed388819bb3f14e8caa9309fd3c2
What is the next step to get the GCC fix in Fedora?
We can either wait for the next release of gcc or we can open a PR with this patch for gcc package.
Lumír
Victor _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproje...
On 12/7/20 1:26 PM, Miro Hrončok wrote:
Hello.
I've been notified that many of the Python interpreters started to fail with new GNU Toolchain (gcc 11, glibc 2.33).
https://koschei.fedoraproject.org/package/pythonX.Y (replace X.Y with version)
Python 3.5 - test_buffer fails on aarch64 - test_buffer+test_dbm_gnu fails on ppc64le - %check segafults on x86_64
Python 3.6 - %check segafults on x86_64 - test_buffer fails on aarch64
Python 3.7 - test_buffer fails on aarch64+ppc64le
Python 3.8 - seems to build fine
Python 3.9 - test_buffer fails on aarch64+ppc64le
Python 3.10 - seems to build fine
FWIW, armv7hl behaves like aarch64.
On 12/7/20 1:26 PM, Miro Hrončok wrote:
Hello.
I've been notified that many of the Python interpreters started to fail with new GNU Toolchain (gcc 11, glibc 2.33).
https://koschei.fedoraproject.org/package/pythonX.Y (replace X.Y with version)
Python 3.5 - test_buffer fails on aarch64 - test_buffer+test_dbm_gnu fails on ppc64le
test_buffer fixed. test_dbm_gnu on ppc64le still fails.
- %check segafults on x86_64
Still segfaults.
Python 3.6 - %check segafults on x86_64
Still segfaults.
- test_buffer fails on aarch64
Fixed.
Python 3.7 - test_buffer fails on aarch64+ppc64le
Fixed.
Python 3.8 - seems to build fine
Still fine.
Python 3.9 - test_buffer fails on aarch64+ppc64le
Fixed.
Python 3.10 - seems to build fine
Still fine.
PyPys have not yet been collected by Koschei, Python 2.7 seems fine.
PyPys and Python 2.7 are fine.
On 12/19/20 2:04 PM, Miro Hrončok wrote:
On 12/7/20 1:26 PM, Miro Hrončok wrote:
Hello.
I've been notified that many of the Python interpreters started to fail with new GNU Toolchain (gcc 11, glibc 2.33).
https://koschei.fedoraproject.org/package/pythonX.Y%C2%A0(replace%C2%A0X.Y%C...)
Python 3.5 - test_buffer fails on aarch64 - test_buffer+test_dbm_gnu fails on ppc64le
test_buffer fixed. test_dbm_gnu on ppc64le still fails.
However, it seem not to be gcc 11 related, because it also fails on Fedora 32 & Fedora 33:
https://koschei.fedoraproject.org/package/python35?collection=f32 https://koschei.fedoraproject.org/package/python3.5?collection=f33
python-devel@lists.fedoraproject.org