]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.14] gh-142342: Fix m68k assembler operand constraints for `%fpcr` access (gh-14234...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Tue, 9 Dec 2025 14:13:31 +0000 (15:13 +0100)
committerGitHub <noreply@github.com>
Tue, 9 Dec 2025 14:13:31 +0000 (14:13 +0000)
commit43f696d942708e059c1400d521d1170a3f9b6af9
treed86b710c57423662c4abb6ea3e4c4bb878070ec7
parent19968c89276e16c20ff8f6916f897f2a19a08daa
[3.14] gh-142342: Fix m68k assembler operand constraints for `%fpcr` access (gh-142343) (#142458)

On m68k, an fmove instruction accessing %fpcr may only move from
or to a data register or a memory operand. The constraint "g" also
permits the use of address registers, which is invalid. The correct
constraint is "dm". Beginning with GCC 15, the register allocator
picks an address register in the code which causes SIGILL during
runtime.
(cherry picked from commit 02c085d48b59c00fb7f4454fb13933e1c2c0b01a)

Co-authored-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Co-authored-by: Michael Karcher <github@mkarcher.dialup.fu-berlin.de>
Include/internal/pycore_pymath.h
Misc/NEWS.d/next/Core_and_Builtins/2025-12-08-13-04-37.gh-issue-142343.BTAyML.rst [new file with mode: 0644]
configure
configure.ac