patches/glibc/ports-2.10.1/590-sh-set-fpscr-proto.patch
| author |
"Yann E. MORIN" <yann.morin.1998@free.fr> |
|
Tue May 08 18:31:10 2012 +0200 (2012-05-08) |
| changeset 2964 |
d48c03998dc1 |
| permissions |
-rw-r--r-- |
scripts: fix catching failures
POSIX 1003.1-2008 does not say whether "set -e" should catch a sub-shell
that exits with !0 (it has a list of conditions to catch, but no list of
conditions not to catch, and this situation is not listed).
bash-3 does not catch such a failure, but bash-4 does. That why, on my
Squeeze system I did not see the issue, while Thomas did on is Lenny chroot.
Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
|
yann@1625
|
1 |
|
|
yann@1625
|
2 |
|
|
yann@1625
|
3 |
diff -durN glibc-2.10.1.orig/sysdeps/sh/sh4/fpu/fpu_control.h glibc-2.10.1/sysdeps/sh/sh4/fpu/fpu_control.h
|
|
yann@1625
|
4 |
--- glibc-2.10.1.orig/sysdeps/sh/sh4/fpu/fpu_control.h 2001-07-06 06:56:04.000000000 +0200
|
|
yann@1625
|
5 |
+++ glibc-2.10.1/sysdeps/sh/sh4/fpu/fpu_control.h 2009-11-13 00:51:26.000000000 +0100
|
|
yann@1625
|
6 |
@@ -45,6 +45,7 @@
|
|
yann@1625
|
7 |
#define _FPU_GETCW(cw) __asm__ ("sts fpscr,%0" : "=r" (cw))
|
|
yann@1625
|
8 |
|
|
yann@1625
|
9 |
#if defined __GNUC__
|
|
yann@1625
|
10 |
+extern void __set_fpscr(unsigned long);
|
|
yann@1625
|
11 |
#define _FPU_SETCW(cw) __set_fpscr ((cw))
|
|
yann@1625
|
12 |
#else
|
|
yann@1625
|
13 |
#define _FPU_SETCW(cw) __asm__ ("lds %0,fpscr" : : "r" (cw))
|