summaryrefslogtreecommitdiff
path: root/numpy/linalg/umath_linalg.c.src
Commit message (Collapse)AuthorAgeFilesLines
* [Road to C++] First step toward numpy/linalg/umath_linalg.c.src conversionserge-sans-paille2022-03-291-4435/+0
| | | | | | As it's a large file, I've first handled the C++ conversion part while keeping Numpy templating system. The switch to C++ template is to be done in another commit.
* BUG: Fix PyInit__umath_linalg typeKazuki Sakamoto2021-12-151-1/+1
| | | | Use PyMODINIT_FUNC instead of PyObject *.
* MAIN: Minor include rationalization.Charles Harris2021-09-031-2/+3
| | | | | | | - Replace "Python.h" by <Python.h> - Replace "structmember.h" by <structmember.h> - Replace <npy_config> by "npy_config" - Define PY_SSIZE_T_CLEAN before all Python.h includes in .c files.
* removed redudancy in codeczgdp18072021-07-101-26/+12
|
* removed redundant functionsczgdp18072021-07-091-67/+49
|
* addressed C reviewsczgdp18072021-06-241-33/+8
|
* refactoring completeczgdp18072021-06-221-145/+60
|
* factored out common init parts for sorgqr, dorgqrczgdp18072021-06-221-109/+57
|
* updated method for finding optimal work_countczgdp18072021-06-091-9/+21
|
* shifted qr code in umath_linalg.c.src aboveczgdp18072021-06-091-426/+425
|
* Take work_count as it isczgdp18072021-06-091-6/+6
|
* fixed title line in release notesczgdp18072021-06-081-6/+0
|
* Addressed reviewsczgdp18072021-06-081-0/+3
|
* removed debug prints and addressed reviewczgdp18072021-06-071-1/+0
|
* removed trailing white spacesczgdp18072021-06-051-14/+14
|
* existing tests passedczgdp18072021-06-051-21/+41
|
* moving intialization outside the loopczgdp18072021-06-051-5/+6
|
* ready for formal addition of tests and documentation updateczgdp18072021-06-041-11/+268
|
* WIPczgdp18072021-06-041-16/+349
|
* ENH: r, raw, economic now accept stacked matricesczgdp18072021-06-031-0/+326
|
* MAINT: Remove uses of PyString_FromString.Charles Harris2020-08-191-1/+1
| | | | | | | | We no longer need to use the compatibility function after dropping support for Python 2.7. In some cases unicode was the correct string type rather than the bytes of the compatibility version and bugs in the array `__complex__` and array `__array_interface__` methods have been fixed by changing that.
* MAINT: Const qualify UFunc inner loops (gh-15355)Kai Striega2020-01-211-34/+34
| | | | | This PR const qualifies the dimension and strides arguments of PyUFuncGenericFunction. Const qualified arguments make it simpler to reason about the behaviour of these ufuncs and prevents accidental mutation. As the const is now required this PR also const qualifies calls to PyUFuncGenericFunction inside the NumPy source code. This closes #15252
* Merge pull request #15333 from eric-wieser/use-PyDict_GetItemWithErrorMatti Picus2020-01-161-8/+20
|\ | | | | BUG: Add some missing C error handling
| * BUG: Add some missing C error handlingEric Wieser2020-01-151-8/+20
| |
* | DOC: fix typosBrian Wignall2020-01-141-1/+1
|/
* MAINT: Remove Python2 specific C module setup (gh-15231)Seth Troisi2020-01-031-16/+3
| | | | | Dropping the support for python 2, the difference in module setup do not have to be accounted for anymore. This removes the macros and ifdef's related to module setup code and python 2 support.
* ENH: update BLAS symbol suffix/prefix handling in cblasfuncs & linalgPauli Virtanen2019-12-141-16/+4
| | | | Revise the BLAS name mangling to support the general scheme.
* ENH: core: add LAPACK64_ support in numpy.linalgPauli Virtanen2019-11-291-265/+276
|
* MAINT: remove duplicate variable assignmentsChristoph Gohlke2019-07-241-2/+0
|
* ENH: Allow use of svd on empty arraysEric Wieser2018-06-271-3/+11
| | | | part of #8654
* Merge pull request #10938 from eric-wieser/linalg-lstsq-ufuncMarten van Kerkwijk2018-05-281-1/+1
|\ | | | | MAINT: One step closer to vectorizing lstsq
| * MAINT: Fix typoEric Wieser2018-04-211-1/+1
| |
* | BUG: optimizing compilers can reorder call to npy_get_floatstatus (#11036)Matti Picus2018-05-091-106/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * BUG: optimizing compilers can reorder call to npy_get_floatstatus * alternative fix for npy_get_floatstatus, npy_clear_floatstatus * unify test with pr #11043 * use barrier form of functions in place of PyUFunc_{get,clear}fperr * update doc, prevent segfault * MAINT: Do some rewrite on the 1.15.0 release notes. [ci skip]
* | Merge pull request #10890 from eric-wieser/linalg-lstsq-ufuncMarten van Kerkwijk2018-04-201-19/+100
|\ \ | |/ | | MAINT: lstsq: compute residuals inside the ufunc
| * MAINT: compute residuals inside the ufuncEric Wieser2018-04-171-19/+100
| | | | | | | | | | | | This prevents an overly large output array being allocated. It also means the the residuals can be handled as a separate out argument in future.
* | Merge pull request #10775 from mdboom/return-errors-from-initEric Wieser2018-04-191-4/+5
|\ \ | |/ |/| BUG: Return NULL from PyInit_* when exception is raised
| * Return NULL from PyInit_* when exception is raisedMichael Droettboom2018-03-301-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | I don't think this is documented anywhere, but I'm pretty sure module init functions should return NULL in order to communicate that an exception occurred during initialization (as is the standard Python/C API convention). It's clear from the CPython code [here](https://github.com/python/cpython/blob/master/Python/importdl.c#L162) that if you don't return NULL, the exception is swallowed and replaced with the message "initialization of %s raised unreported exception". Admittedly, this is only useful for people porting Numpy to new platforms where it is helpful to know where module initialization is failing, but it can't hurt.
* | ENH: Add raw ufuncs to interface to gelsd functionsEric Wieser2018-04-101-8/+94
| |
* | ENH: Add wrapper functions to allocate workspacesEric Wieser2018-04-101-0/+308
| |
* | ENH: Add missing cgelsd and sgelsd routineslapack_lite code generator2018-04-101-0/+14
|/
* MAINT: Hard tab and whitespace cleanup.Charles Harris2018-03-081-1/+1
|
* MAINT: Fix sign-compare warnings in umath_linalg.Charles Harris2018-01-161-29/+20
| | | | | | | | | | | The sign-compare warning is enabled for python 3.5+ builds and the warnings have been causing wheel build failures on travis ci. The replacements here of `size_t` and `ptrdiff_t` by `npy_intp` should be safe given that the sizes of numpy arrays in bytes are specified by those types. A bigger problem is that most BLAS libraries are compiled with smaller integer types. I don't know where that is checked, or even if it is checked.
* BUG: prototypes for [cz]dot[uc] are incorrectEric Wieser2017-11-101-8/+8
| | | | F2C does not support complex return values.
* ENH: Spelling fixesVille Skyttä2017-05-091-1/+1
|
* STY: Fix bad style in umath_linalg (#8825)Eric Wieser2017-03-251-222/+242
| | | | | | | | | | | | | | | | * STY: Fix missing braces and spaces * STY: Use NPY_INLINE not inline * MAINT: Bump umath_linalg version, after #8756 * STY: Wrap long lines * STY: Spaces around assignment and comparison * DOC: fix incorrect description of svd overloads * STY: Use ternary operator in min and max
* MAINT: Always use parameter structs to call lapackEric Wieser2017-03-241-141/+153
| | | | | Getting the arguments to lapack calls in the correct order in two places is harder than doing it in one.
* MAINT: Move definitions of call_ before init_Eric Wieser2017-03-241-103/+103
| | | | | | | | This diff makes it look like something else has happened, but in reality that's the only change here. This means we can invoke call_@lapack_func@ in init_@lapack_func@ when we do workspace size calculations
* BUG: Correctly compute the LDA parameters for lapack callsEric Wieser2017-03-241-27/+57
| | | | | These are documented in the lapack source code as always being one or greater. LD stands for "leading dimension", and can be thought of as a stride.
* BUG: Work around bugs in LAPACK 3.0.0Eric Wieser2017-03-241-0/+5
|
* MAINT: more consistent notation in umath_linalgalex2015-05-211-5/+13
|
View Lorry Controller Status