bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why require SLOW_BUT_NO_HACKS for stubs?


From: John Spencer
Subject: Re: Why require SLOW_BUT_NO_HACKS for stubs?
Date: Tue, 12 Jun 2012 14:05:05 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110221 SUSE/3.1.8 Mail/1.0

Please don't forget fseterr, the other rude #erroring spot which fails even though there is deactivated portable fallback code.

Subject: [PATCH] 6 syscalls is still better than a failed build

---
 lib/fseterr.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lib/fseterr.c b/lib/fseterr.c
index eaad702..37efa4f 100644
--- a/lib/fseterr.c
+++ b/lib/fseterr.c
@@ -45,7 +45,7 @@ fseterr (FILE *fp)
   fp->_Mode |= 0x200 /* _MERR */;
 #elif defined __MINT__              /* Atari FreeMiNT */
   fp->__error = 1;
-#elif 0                             /* unknown  */
+#elif 1                             /* unknown  */
   /* Portable fallback, based on an idea by Rich Felker.
      Wow! 6 system calls for something that is just a bit operation!
Not activated on any system, because there is no way to repair FP when
--
1.7.3.4




reply via email to

[Prev in Thread] Current Thread [Next in Thread]