From: Akim Demaille Date: Tue, 28 Aug 2001 09:05:29 +0000 (+0000) Subject: * doc/autoconf.texi (Function Portability): Mention C right shifts. X-Git-Tag: AUTOCONF-2.52d~30 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=b590bcbea9e9ba701309646c0b1f497acd5e9fda;p=thirdparty%2Fautoconf.git * doc/autoconf.texi (Function Portability): Mention C right shifts. --- diff --git a/ChangeLog b/ChangeLog index 886dadc4b..2a97a882b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,7 @@ +2001-08-28 Kevin Ryde + + * doc/autoconf.texi (Function Portability): Mention C right shifts. + 2001-08-27 Tim Van Holder * lib/autotest/general.m4: Reword some messages. diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 038e8fdb0..33e5380e4 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -3373,6 +3373,13 @@ that are open. For example, on Windows 9x and ME, such a call would fail; on DOS it could even lead to file system corruption, as the file might end up being written to after the OS has removed it. +@item Signed @code{>>} +Normally the C @code{>>} right shift of a signed type replicates the +high bit, giving a so-called ``arithmetic'' shift. But care should be +taken since the ISO C standard doesn't require that behaviour. On those +few processors without a native arithmetic shift (for instance Cray +vector systems) zero bits may be shifted in, the same as a shift of an +unsigned type. @end table