numpy / numpy/numpy

BUG: Dispatcher does not detect instruction set on WoA

Open
#29,458 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

00 - Bug
Dominant language
Python
Stars
32.8k
Forks
12.8k
Avg merge
1d 7h
Merged PRs (30d)
197

Description

Describe the issue:

Was investigating #29442 and found that the architecture detection logic for WoA is non-functional.

Reproduce the code example:

none needed - use show_runtime

Python and NumPy Versions:
2.3.2
3.12.10 (tags/v3.12.10:0cc8128, Apr  8 2025, 12:31:18) [MSC v.1943 64 bit (ARM64)]

and

2.3.2
3.12.3 (main, Jun 18 2025, 17:59:45) [GCC 13.3.0]
Runtime Environment:
[{'numpy_version': '2.3.2',
  'python': '3.12.10 (tags/v3.12.10:0cc8128, Apr  8 2025, 12:31:18) [MSC '
            'v.1943 64 bit (ARM64)]',
  'uname': uname_result(system='Windows', node='BOOK-NV3Q5DD1QM', release='11', version='10.0.26100', machine='ARM64')},
 {'simd_extensions': {'baseline': ['NEON', 'NEON_FP16', 'NEON_VFPV4', 'ASIMD'],
                      'found': [],
                      'not_found': ['ASIMDHP', 'ASIMDFHM']}}]

and

[{'numpy_version': '2.3.2',
  'python': '3.12.3 (main, Jun 18 2025, 17:59:45) [GCC 13.3.0]',
  'uname': uname_result(system='Linux', node='BOOK-NV3Q5DD1QM', release='6.6.87.1-microsoft-standard-WSL2', version='#1 SMP PREEMPT_DYNAMIC Mon Apr 21 17:10:52 UTC 2025', machine='aarch64')},
 {'simd_extensions': {'baseline': ['NEON', 'NEON_FP16', 'NEON_VFPV4', 'ASIMD'],
                      'found': ['ASIMDHP', 'ASIMDFHM'],
                      'not_found': ['SVE']}},
 {'architecture': 'armv8',
  'filepath': '/home/andrew/tmp/venv/lib/python3.12/site-packages/numpy.libs/libscipy_openblas64_-71e1b124.so',
  'internal_api': 'openblas',
  'num_threads': 12,
  'prefix': 'libscipy_openblas',
  'threading_layer': 'pthreads',
  'user_api': 'blas',
  'version': '0.3.30'}]
Context for the issue:

These are the same machine. There have been issues w/ reproduction of some crashes, and dispatch not working properly does not help.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running show_runtime on the reported Windows ARM64 and Linux WSL environments and compare the instruction-set and architecture output. Trace the architecture detection path responsible for the discrepancy; done means WoA reports its instruction set consistently instead of omitting the architecture information.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.