The problem seems to be in boolean indexing.

Can you share a gdb traceback?

Can you share a gdb traceback?

I was going to wait on the next GCC 15 version. Fedora (and Linus!) jumped the gun in using 15 in a release.

I can reproduce segfaults on a small chunk of the testsuite (and, well, in production, which is what led me to double-check ;p) with GCC 15.1.0 over here, too, FWIW (Gentoo Linux, x64, on a zen4 CPU). Everything passes w/ GCC 14.x (right now, 14.3.0).

Will see about getting some traces in the next few days.

I was going to wait on the next GCC 15 version. Fedora (and Linus!) jumped the gun in using 15 in a release.

Fedora only shipped it briefly before the final release. The next GCC 15 release will be in a couple of months, then it goes to yearly (same schedule as usual). It's best if it turns out to be a GCC bug to get it reported before that next one. Otherwise, relying on the fix being out there takes way longer.

I tried to reproduce this in the following environments:

• on my regular Gentoo workstation using GCC trunk but with -O3 -march=znver2 -flto with our numpy-2.2.6 package's testsuite
• in a clean Gentoo container running stable but with GCC 15 installed and in-use to build our numpy-2.5.5 package's testsuite
• in a Fedora 42 container (fedora:42 with Docker) on a git clone of main using spin test
  and all of them worked.

@NiLuJe Feel free to file a bug on the Gentoo side so we can dig into it a bit there and see if we can come up with something to share on this side if there's nothing obvious we find here. If you do, please include the testsuite results when run via the ebuild (inc. build.log) and emerge --info. Thanks!