From 104ad066af2c9226a0510431513999365420fd1d Mon Sep 17 00:00:00 2001 From: Martin Kroeker Date: Fri, 30 Dec 2016 00:45:59 +0100 Subject: [PATCH] Use appropriate int32/int64 format for error number in message string --- driver/others/xerbla.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/driver/others/xerbla.c b/driver/others/xerbla.c index 7427b51c4..4f26042b7 100644 --- a/driver/others/xerbla.c +++ b/driver/others/xerbla.c @@ -46,10 +46,16 @@ #define printf _cprintf #endif +#ifdef INTERFACE64 +#define MSGFMT " ** On entry to %6s parameter number %2d had an illegal value\n" +#else +#define MSGFMT " ** On entry to %6s parameter number %2ld had an illegal value\n" +#endif + #ifdef __ELF__ int __xerbla(char *message, blasint *info, blasint length){ - printf(" ** On entry to %6s parameter number %2d had an illegal value\n", + printf(MSGFMT, message, *info); return 0; @@ -61,7 +67,7 @@ int BLASFUNC(xerbla)(char *, blasint *, blasint) __attribute__ ((weak, alias ("_ int BLASFUNC(xerbla)(char *message, blasint *info, blasint length){ - printf(" ** On entry to %6s parameter number %2d had an illegal value\n", + printf(MSGFMT, message, *info); return 0;