[MacPorts] #66129: Pythons are broken for +universal, even on Intel with Clang
MacPorts
noreply at macports.org
Tue Nov 1 11:30:59 UTC 2022
#66129: Pythons are broken for +universal, even on Intel with Clang
--------------------------------------------+----------------------
Reporter: barracuda156 | Owner: jmroot
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.0
Resolution: | Keywords:
Port: python310, python39, python38 |
--------------------------------------------+----------------------
Comment (by kencu):
looks like an ICE with this old clang, involving atomics perhaps?
{{{
1473 :fatal error: error in backend: Cannot select: 0x10268f210: i8,ch
= AtomicLoad 0x1028e77e8, 0x10268f510<Volatile LD1[@is_tripped.0]> [ID=11]
1474 :info:build 0x10268f510: i64 = X86ISD::WrapperRIP 0x10268c210
[ID=10]
1475 :info:build 0x10268c210: i64 = TargetGlobalAddress<i1*
@is_tripped.0> 0 [ID=8]
1476 :info:build In function: _PyErr_CheckSignalsTstate
1477 :info:build clang: error: clang frontend command failed with exit
code 70 (use -v to see invocation)
}}}
I don’t see this is likely fixable, so probably have to blacklist this
clang version if someone else can reproduce this error.
Noted it builds fine non-universal 64-bit with this compiler:
https://build.macports.org/builders/ports-10.8_x86_64-builder/builds/104825
--
Ticket URL: <https://trac.macports.org/ticket/66129#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list