summaryrefslogtreecommitdiff
path: root/numpy/distutils
Commit message (Collapse)AuthorAgeFilesLines
* DEV: supporting IBM i systemGavinZhang2022-08-143-3/+16
|
* remove unneeded future importsJake Bowhay2022-07-172-4/+0
|
* BUG: Use `Popen` to silently invoke f77 -vMichael Osthege2022-07-091-1/+7
| | | | | | The output analyzed by this function unexpectedly ended up in stderr. Closes #21942
* Fix lib flags for librandomMatthew Brett2022-06-291-0/+18
| | | | | Add the voltbl fix to librandom. Remove SSE flag for GCC on 32-bit Windows, it's the default.
* Fix a potential variable misuse bugJingxuan He2022-06-151-1/+1
|
* BUG, SIMD: Fix detecting NEON/ASIMD on aarch64Sayed Adel2022-06-141-1/+1
|
* fix upSayed Adel2022-06-091-1/+1
|
* BLD, SIMD: Fix detecting armhfSayed Adel2022-06-091-21/+46
| | | | | | Strictly detects armhf via compiler definitions, to avoid building neon objects on arch armel even when the compiler supports armv7 features on it.
* BLD, SIMD: Hardened the Neon/ASIMD compile-time testsSayed Adel2022-06-097-26/+38
| | | | | | Avoid passing any constants or traced pointers to avoid compiler optimizations, so we make the sure the required instructions have been tested against the linker.
* shorten linei-shenl2022-06-081-2/+2
|
* Enable fortran preprocessing on Windowsi-shenl2022-06-081-1/+2
| | | | | Especially needed for compiling scipy on Windows. On Linux and Mac, fortran preprocessing is already enabled.
* MAINT: Python <3.8 related cleanupsBrigitta Sipőcz2022-05-231-6/+1
|
* MAINT: Python <3.7 related cleanupsBrigitta Sipőcz2022-05-231-2/+1
|
* Questionable removal of python <3.6 related thingsBrigitta Sipocz2022-05-171-3/+0
|
* Remove python <3.6 related thingsBrigitta Sipocz2022-05-171-4/+1
|
* Merge pull request #21452 from seberg/cleanup-test-outputMatti Picus2022-05-061-1/+3
|\ | | | | TST: Remove most prints from the test suit run
| * TST: Remove most prints from the test suit runSebastian Berg2022-05-051-1/+3
| | | | | | | | | | | | | | | | Pytest silence these normally anyway (capturing it to print it only on failure), but occasionally I run with `-s` and I don't think this output adds anything unless using printing to debug a specific test. If nobody else cares about it nvm, just close it :). Otherwise this cleans up everything in the fast tests, except the f2py compilation right now.
* | BUG: Ensure compile errors are raised correcltySebastian Berg2022-05-051-1/+2
|/ | | | | | | | | | | This has been bugging me for a bit. The concurrent.futures Executor requires checking the result for the error to be raised. That makes sense, but just means we need to consume the result explicitly here to ensure we know about compile errors. Otherwise, compile errors just pass silently (which is very confusing if the old object files are still around and the tests run based on the old version).
* Fix issue probably-meant-fstring found at https://codereview.doctorcode-review-doctor2022-04-231-1/+1
|
* Merge pull request #21306 from serge-sans-paille/feature/syndicate-cxxflagsMatti Picus2022-04-081-0/+8
|\ | | | | Introduce numpy.core.setup_common.NPY_CXX_FLAGS
| * Introduce numpy.core.setup_common.NPY_CXX_FLAGSserge-sans-paille2022-04-081-0/+8
| | | | | | | | | | | | | | | | | | 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
* | Add space after argument nameOscar Gustafsson2022-04-032-18/+18
|/
* Merge pull request #20991 from r-devulap/exp-log-svmlMatti Picus2022-03-231-1/+1
|\ | | | | ENH: Use SVML for f64 exp and log
| * BUILD: Disable MMX registers when building with -mavx512fRaghuveer Devulapalli2022-02-281-1/+1
| | | | | | | | | | | | 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.
* | road-to-cxx: x86-qsort.dispatch.c.src -> x86-qsort.dispatch.cppserge-sans-paille2022-02-211-0/+2
| | | | | | | | | | | | | | Actual c++ification. Also fix a slight bug in numpy/distutils/ccompiler_opt.py when intermediate directory is missing.
* | MAINT: point to html docs on distutils migration in deprecation messageRalf Gommers2022-02-181-1/+2
| | | | | | | | [skip azp]
* | MAINT: fix failure due to importing warnings in `distutils/__init__.py`Ralf Gommers2022-02-161-0/+1
| |
* | DEP: deprecate `numpy.distutils`, and add a migration guideRalf Gommers2022-02-151-0/+11
| |
* | BUG: use ThreadPoolExecutor instead of ThreadPoolGalaxySnail2022-02-101-4/+3
|/ | | | | | | Use `concurrent.futures.ThreadPoolExecutor` in distutils instead of `multiprocessing.pool.ThreadPool`. Fix #21026
* DOC: improper doc syntax (markdown and imbalanced ticks). (#20944)Matthias Bussonnier2022-01-301-1/+1
| | | | | | | | | | | | | | | | | | 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.
* Fix build_ext interaction with non numpy extensionsserge-sans-paille2022-01-281-2/+2
| | | | | | | | Numpy extensions define the extra_cxx_compile_args and extra_c_compile_args filed, but distutils extensions don't. Take that into account when populating build_extension. Should fix #20928
* BUG: distutils: fix building mixed C/Fortran extensionsRalf Gommers2022-01-241-7/+23
| | | | | | | | | | | | In SciPy we had a couple of cases where we build a Python extension with C source files but linked against static libraries built from Fortran code. Those should be using the Fortran linker, but this was broken in 1.22.0 by gh-19713 (the PR that introduced C++ in NumPy). This fixes a few issues in the `build_ext` command, and documents better what is going on there. Should close SciPy issues 8325 and 15414.
* TST: Add CPU dispatch/baseline tests for VSX4Rafael Cardoso Fernandes Sousa2022-01-172-7/+7
|
* STY: Fix linter issueRafael Cardoso Fernandes Sousa2022-01-141-1/+2
|
* ENH: Add CPU feature detection for VSX4 (Power10)Rafael Cardoso Fernandes Sousa2022-01-134-1/+42
|
* MAINT, DOC: fix new typos detected by codespellDimitri Papadopoulos2022-01-121-1/+1
|
* Merge pull request #20416 from ARCCA/armcompilerMatti Picus2021-12-245-5/+163
|\ | | | | ENH: Add ARM Compiler with ARM Performance Library support
| * Update armccompiler.pyThomas Green2021-12-141-3/+3
| | | | | | Remove `-mcpu=native` since it should be decided by the configuration.
| * Merge branch 'numpy:main' into armcompilerThomas Green2021-12-083-13/+22
| |\
| * | Update __init__.pyThomas Green2021-12-021-2/+3
| | |
| * | Update armccompiler.pyThomas Green2021-12-021-7/+12
| | |
| * | Update system_info.pyThomas Green2021-12-021-6/+5
| | |
| * | Add armpl as blas/lapack providerThomas Green2021-11-161-3/+57
| | | | | | | | | Add support for ARMPL - requires ARMPL_DIR set - product page https://www.arm.com/products/development-tools/server-and-hpc/allinea-studio/performance-libraries
| * | Create arm.pyThomas Green2021-11-161-0/+73
| | | | | | | | | Added `-fPIC` due to relocation errors.
| * | Update __init__.pyThomas Green2021-11-161-1/+1
| | |
| * | Update ccompiler.pyThomas Green2021-11-161-0/+3
| | | | | | | | | Added ARM compiler.
| * | Create armccompiler.pyThomas Green2021-11-161-0/+23
| | | | | | | | | | | | | | | From https://gitlab.com/arm-hpc/packages/-/wikis/packages/numpy Added `-fPIC` due to relocation errors when building shared library from static library such as quadmath.
* | | BUG: Support env argument in CCompiler.spawnIsuru Fernando2021-12-221-3/+5
| | |
* | | BUG, DIST: fix normalize IBMZ features flagsSayed Adel2021-12-152-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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']
* | | TST: expend ccompiler tests to cover s390x featuresSayed Adel2021-12-141-30/+45
| | |
View Lorry Controller Status