| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
The fact we're obliged to allow `if NPY_TITLE_KEY(...) {` for compatibility doesn't mean we have to keep using the old spelling ourself.
|
|\
| |
| | |
ENH: Use AVX-512F for complex number arithmetic, absolute, square and conjugate
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
ENH: improve runtime detection of CPU features
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Put the old CPU detection code to rest
The current CPU detection code only supports x86 and
it's count on compiler built-in functions that not widely supported
by other compilers or platforms.
NOTE: `npy_cpu_supports` is removed rather than deprecated,
use the macro `NPY_CPU_HAVE(FEATURE_NAME_WITHOUT_QUOTES)` instead.
- Initialize the new CPU features runtime detector
Almost similar to GCC built-in functions,
so instead of `__builtin_cpu_init`, `__builtin_cpu_supports`
its provide `npy_cpu_init`, `npy_cpu_have` and `NPY_CPU_HAVE`.
NOTE: `npy_cpu_init` must be called before any use of
`npy_cpu_have` and `NPY_CPU_HAVE`, however `npy_cpu_init`
already called during the load of module `umath`
so there's no reason to call it again in most of the cases.
- Add X86 support
detect almost all x86 features, also provide
CPU feature groups that gather several features.
e.g. `AVX512_KNM` detect Knights Mill's `AVX512` features
- Add IBM/Power support
only supports Linux and count here on `glibc(getauxval)`
to detect VSX support and fail-back to the compiler definitions
for other platforms.
- Add ARM support
Same as IBM/Power but its parse `/proc/self/auxv`
if `glibc(getauxval)` isn't available.
- Update umath generator
- Add testing unit for Linux only
- Add new attribute `__cpu_features__` to umath module
`__cpu_features__` is a dictionary contains all supported
CPU feature names with runtime availability
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
If these can't do the work that is requested, then we should fail loudly, at least during development.
Really the API of these methods is wrong - they should take a `PyArray_Descr`, not an array.
|
|\ \ \
| | | |
| | | | |
MAINT: Use True/False instead of 1/0 in np.dtype.__reduce__
|
| | | |
| | | |
| | | |
| | | | |
This doesn't really make much difference, but is a little more correct, a little faster, and produces two fewer bytes of pickle data.
|
|\ \ \ \
| | | | |
| | | | | |
TST: mark the top 3 slowest tests to save ~10 seconds
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
ENH: fixing generic error messages to be more specific in multiarray/descriptor.c
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| |/ / / / |
|
| | | | | |
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
report_generic
* 'report_generic' of https://github.com/ericmariasis/numpy:
Update numpy/core/src/multiarray/descriptor.c
Update numpy/core/src/multiarray/descriptor.c
Update numpy/core/src/multiarray/descriptor.c
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| |/ / / / |
|
| |/ / / |
|
|\ \ \ \
| | | | |
| | | | | |
[DOC] Mention behaviour of np.squeeze with one element
|
| | | | |
| | | | |
| | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| |\ \ \ \ \
| | |/ / / /
| |/| | | /
| | | |_|/
| | |/| | |
|
| | |/ /
| |/| | |
|
|\ \ \ \
| |_|/ /
|/| | | |
DEP: Schedule unused C-API functions for removal/disabling
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This function is currently undocumented. It is not used in NumPy
and seems useless outside of NumPy. This is due to the fact that
user datatypes are not actually capable of leveraging this function!
They are stored in a different way, so that their loops cannot be
identified by an index.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This function provides mainly the same API as PyObject_Call()
with the exception of skipping ufunc overrides and output array
wraps.
It is fairly unwieldy to use, since ownership of all inputs and
outputs is transferred, but otherwise it still uses args and kwargs
as inputs.
As such, no known usage exists and PyObject_Call seems a reasonable
replacement for possible usage. Keeping it around means that we would
may have to add tests or risk breaking this function when ufunc
code is refactored.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The function has no known usage outside of NumPy. It is fairly
complex to use due to how it behaves with scalars, and, at least
with a given "flexible" dtype would require additional access
to the private PyArray_AdaptFlexibleDType function.
Removing the function from public API will simplify refactor work
of the dtype and dimension recovery.
|
|\ \ \ \
| | | | |
| | | | | |
ENH: Use AVX-512F for np.maximum and np.minimum
|