blob: bdf0b9058f7ed5296740a88444691e46d0feac2c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
#include "Python.h"
/*
* From f2c.h, this should be safe unless fortran is set to use 64
* bit integers. We don't seem to have any good way to detect that.
*/
typedef int integer;
/*
From the original manpage:
--------------------------
XERBLA is an error handler for the LAPACK routines.
It is called by an LAPACK routine if an input parameter has an invalid value.
A message is printed and execution stops.
Instead of printing a message and stopping the execution, a
ValueError is raised with the message.
Parameters:
-----------
srname: Subroutine name to use in error message, maximum six characters.
Spaces at the end are skipped.
info: Number of the invalid parameter.
*/
int xerbla_(char *srname, integer *info)
{
static const char format[] = "On entry to %.*s" \
" parameter number %d had an illegal value";
char buf[sizeof(format) + 6 + 4]; /* 6 for name, 4 for param. num. */
int len = 0; /* length of subroutine name*/
#ifdef WITH_THREAD
PyGILState_STATE save;
#endif
while( len<6 && srname[len]!='\0' )
len++;
while( len && srname[len-1]==' ' )
len--;
#ifdef WITH_THREAD
save = PyGILState_Ensure();
#endif
PyOS_snprintf(buf, sizeof(buf), format, len, srname, *info);
PyErr_SetString(PyExc_ValueError, buf);
#ifdef WITH_THREAD
PyGILState_Release(save);
#endif
return 0;
}
|
