| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
ENH: add support for fujitsu C/C++ compiler and SSL2 to numpy.
|
| | |
|
|\ \
| |/
|/| |
BLD: Add compile and runtime checks for AVX512_SPR
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
| |
1. FreeBSD uses elf_aux_info() instead of getauxval.
2. Switch to using compiler macros for detecting POWER platform
FreeBSD sets the machine name (what uname -m prints) on all powerpc* to
just powerpc. To identify actual architecture, uname -p should be used,
but this is not present in uname() function. Thus, the only way to
correctly detect platform is to use what uname prints and also check
compiler defines.
|
| |
|
|
|
|
|
|
| |
Strictly detects armhf via compiler definitions,
to avoid building neon objects on arch armel even when
the compiler supports armv7 features on it.
|
|\
| |
| | |
Introduce numpy.core.setup_common.NPY_CXX_FLAGS
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Group all C++ flags in one location.
This avoids redundancy and makes sure we test the flags we use, and use the
flags we test.
Fix #21302
|
|/ |
|
|\
| |
| | |
ENH: Use SVML for f64 exp and log
|
| |
| |
| |
| |
| |
| | |
Work around for a bug in gcc compiler. When using several kmask
variables __mmask16/__mmask8, the compiler sometimes uses %mmx registers
to save them on to the stack which corrupts the x87 stack.
|
|/
|
|
|
|
|
| |
Actual c++ification.
Also fix a slight bug in numpy/distutils/ccompiler_opt.py when intermediate
directory is missing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here are two modifications:
The first one is the inclusion of markdown fence blocks in the middle of
RST. While this is not really a problem for current documentation as
this is a private function, it still makes other RST parser choke on
this.
In particular this is seen as a tile as it is a text line followed by
a line of only backticks, and that makes my new project to show better
docstrings in Jupyter fails.
I can locally exclude this function, but while not fix it to show good
examples ?
Second, while grepping for triple backticks I found that there are a
stray one in another place.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The normal behavior is to erase any flag that starts with
`-m[a-z0-9\-\.]` when flag `-march` or `-mcpu` specified. for example:
cc_normalize_flags([
'-msse', '-msse2', '-msse3', '-mssse3', '-march=core-avx2'
])
should be normalized to: ['-march=core-avx2']
but in the case of `s390x`, on GCC flag `-march=arch[0-9]` doesn't implies flag
`-mzvector` which is required to enable zvector api. for example:
cc_normalize_flags([
'-mzvector', '-march=arch11', '-march=arch12', '-march=arch13']
)
should be normalized to: ['-mzvector', '-march=arch13']
instead of: ['-march=arch13']
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We would like to extend CPU feature detection infrastructure
for IBM Z CPU features. Eventually It will help to add and
enable Z specific SIMD builtins and instructions.
As part of the PR, we have extended ccompiler_opt.py,
npy_cpu_features.c.src, npy_cpu_features.h, other files for
Z CPU feature detection and added test files for VX/VXE/VXE2
in distutils/checks.
|
|
|
|
|
|
|
| |
`load_module` is deprecated since python 3.4 and will be removed in python 3.12.
Use `exec_module` instead. Provide a convenience function in `distutils.misc_utils`
instead of `npy_load_module` from `compat.py3k`.
|
|\
| |
| | |
BUG, DIST: Print os error message when the executable not exist
|
| |
| |
| |
| |
| |
| | |
this patch is really important since most of the users aren't able to determine
the build error when the toolchain or the built environment missing
executable files of compiler, linker, assembler, etc.
|
|/
|
|
|
|
|
| |
Otherwise it gets used for C source too, which is either useless or invalid (for
clang(family compiler)
Fix #20335
|
|
|
|
|
|
|
|
|
| |
* Don't pass /arch:SSE2 to MSVC link targeting x64
* Fix test
* Fix format
* Fix one more test
|
|\
| |
| | |
MAINT: Remove unused imports and remove duplicated tests
|
| | |
|
| | |
|
|/
|
|
|
| |
This is just a technical prototype to measure and discuss the impact and
implication of moving to C++ for kernel code generation.
|
| |
|
|
|
|
|
|
|
| |
In certain cases `-Werror` gets skipped during the availability test due
to "unused arguments" warnings. To solve the issue, `-Werror-implicit-function-declaration`
was added as a secondary flag, which is enough to guarantee the sanity of the testing process
when it comes to testing the availability of certain intrinsics.
|
|
|
|
|
|
|
|
| |
Unlike GCC and CLANG, Intel Compiler exposes all supported intrinsics,
whether or not the build options for those features are specified.
Therefore, we must test #definitions of CPU features when option native/host
is enabled via `--cpu-baseline` or through env var `CFLAGS` otherwise
the test will be broken and leads to enable all possible features.
|
| |
|
|
|
|
|
|
|
|
|
| |
The bug can occur only if the build option `build`
was passed before the option `bdist_wheel`.
You may still realize a duplicate printing for the compiler
optimization report in the build log, which is normal due to
multiple calling of command `build` by setuptools.
|
|
|
|
|
| |
Same usage as the C dispatch-able sources except files extensions
should be `.dispatcher.cpp` or `.dispatch.cxx` rather than `.dispatch.c`
|
| |
|
|
|
|
|
|
| |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
Co-authored-by: h-vetinari <h.vetinari@gmx.com>
Co-authored-by: Derek Homeier <dhomeie@gwdg.de>
|
|
|
|
|
|
|
|
|
|
| |
The new path becomes `build/src.*/numpy/distutils/include/npy_cpu_dispatch_config.h`
instead of `numpy/core/src/common/_cpu_dispatch.h`.
The new path allows other projects to re-use the CPU dispatcher
once we decide to expose the following headers:
- `numpy/core/src/common/npy_cpu_dispatch.h`
- `numpy/core/src/common/npy_cpu_features.h`
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* replace superfluous single-character regex character
classes with their literal string equivalents; this
avoids the overhead associated with a character class
when there's only a single character enclosed (so there's
no benefit to the class overhead)
* for more information see:
Chapter 6 of:
Friedl, Jeffrey. Mastering Regular Expressions. 3rd ed.,
O’Reilly Media, 2009.
|
| |
|
|
|
|
| |
Co-authored-by: h-vetinari <h.vetinari@gmx.com>
|
| |
|
| |
|
|\
| |
| | |
DOC: Fix docstring cross-referencing
|
| | |
|
| |
| |
| | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
|/
|
|
|
|
|
|
| |
- Extending Distutils::CompilerOpt to allow adding extra separate test cases
related to a certain CPU feature without affecting its availability.
- Add test cases for reduce intrinsics and AVX512BW mask operations, they can be
reached through C #defentions NPY_HAVE_AVX512BW_MASK and NPY_HAVE_AVX512F_REDUCE.
|