Re: git: b0b4d9e1eae8 - main - */*: Switch to NumPy 2.x

Vladimir Druzenko wrote:
> 13.05.2026 21:10, Max Brazhnikov пишет:
>> On Mon, 11 May 2026 17:40:13 -0400 Charlie Li wrote:
>>> Vladimir Druzenko wrote:
>>>> 11.05.2026 22:29, Charlie Li пишет:
>>>>> The base system can claim support for older CPU however it wants, but
>>>>> it does not mean individual third-party software has to do the same.
>>>>> Of course we in ports should make our best efforts in this regard but
>>>>> the expected majority use-cases and configurations need to take
>>>>> precedence.
>>>>>
>>>>> I'm not opposed to an option that makes clear that -Dcpu-baseline=none
>>>>> is both not the default and strongly discouraged outside of CPUs older
>>>>> than or lack features of -Dcpu-baseline=min.
>>>> How many years to wait for the "right" decision?
>>>>
>>> Whoever wants to implement an option following this description before
>>> me or another python@ member gets to it is welcome to submit a diff for
>>> consideration.
>> We either should officially drop support for CPU without SSE for packages
>> or add -Dcpu-baseline=none to numpy port by default.
> There's some strange situation there - either SSE4.2 or no SSE, 
> including SSE1 and SSE2, which are present in all CPUs that support amd64.
> 
Pentium and Celeron from the Nehalem/Westmere generation do not support 
SSE4.1, SSE4.2 and POPCNT despite implementing the rest of X86_V2.>> We 
may also add OPTIMIZED_CFLAGS or whatever option to build numpy with
>> -Dcpu-baseline="native" and -Dcpu-dispatch="none".
> Check patch please.
> 
As previously explained, the default cannot be -Dcpu-baseline=none.

While I shake my fist at Intel for playing market segmentation down to 
the CPU instruction level, the reality is that the numpy project decided 
to prioritise hardware configurations for the vast majority of users. 
X86_V2 was made default for the 2.4 branch: 
https://github.com/numpy/numpy/issues/27851

-- 
Charlie Li
...nope, still don't have an exit line.