On Thu, May 08, 2025 at 09:30:34AM +0100, Stuart Henderson wrote:
> On 2025/05/08 10:09, Theo Buehler wrote:
> > On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote:
> > > The main blocker for the update used to be boost. But now that we have
> > > boost 1.87 I think it's a good time to update numpy to the 2.x series. The
> > > diff below gets us to 2.0.2.
> >
> > Hits an ICE on aarch64:
> >
> > ../numpy/_core/src/umath/loops_autovec.dispatch.c.src:107:43: internal compiler error: Segmentation fault
>
> https://github.com/numpy/numpy/issues/27699#issuecomment-2692261936
Yes that works around the issue:
= 89 failed, 43745 passed, 329 skipped, 2789 deselected, 59 xfailed, 4 xpassed, 64 warnings in 484.61s (0:08:04) =
This looks about as usual for aarch64. Short summary after the patch.
Index: patches/patch-numpy__core_src_umath_loops_autovec_dispatch_c_src
===================================================================
RCS file: patches/patch-numpy__core_src_umath_loops_autovec_dispatch_c_src
diff -N patches/patch-numpy__core_src_umath_loops_autovec_dispatch_c_src
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ patches/patch-numpy__core_src_umath_loops_autovec_dispatch_c_src 8 May 2025 08:35:56 -0000
@@ -0,0 +1,17 @@
+Index: numpy/_core/src/umath/loops_autovec.dispatch.c.src
+--- numpy/_core/src/umath/loops_autovec.dispatch.c.src.orig
++++ numpy/_core/src/umath/loops_autovec.dispatch.c.src
+@@ -104,11 +104,13 @@ NPY_NO_EXPORT void NPY_CPU_DISPATCH_CURFX(@TYPE@_right
+
No comments:
Post a Comment