Do not assume EMACS_INT is the same width as a pointer.

This prepares for a future patch that will prefer 64-bit EMACS_INT if
available.  That patch can be tried now, by compiling with -DWIDE_EMACS_INT,
but it is temporarily not the default so that it can be further tested.

Also, install some other fixes for problems discovered by the static
checking of GCC 4.6.0.

Fixes: debbugs:8545 debbugs:8601 debbugs:8600 debbugs:8602

2 files changed, 8 insertions, 3 deletions

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 4aa63c6abaa..7ef3be46b68 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2011-05-06  Paul Eggert  <eggert@cs.ucla.edu>
+
+        * numbers.texi (Integer Basics): Large integers are treated as floats.
+
 2011-04-30  Lars Magne Ingebrigtsen  <larsi@gnus.org>
 
         * processes.texi (Synchronous Processes): Document the (:file
diff --git a/doc/lispref/numbers.texi b/doc/lispref/numbers.texi
index 23150c2c937..2c73a03a26c 100644
--- a/doc/lispref/numbers.texi
+++ b/doc/lispref/numbers.texi
@@ -55,14 +55,15 @@ chapter assume an integer has 30 bits.
 @cindex overflow
 
   The Lisp reader reads an integer as a sequence of digits with optional
-initial sign and optional final period.
+initial sign and optional final period.  An integer that is out of the
+Emacs range is treated as a floating-point number.
 
 @example
  1               ; @r{The integer 1.}
  1.              ; @r{The integer 1.}
 +1               ; @r{Also the integer 1.}
 -1               ; @r{The integer @minus{}1.}
- 1073741825      ; @r{Also the integer 1, due to overflow.}
+ 1073741825      ; @r{The floating point number 1073741825.0.}
  0               ; @r{The integer 0.}
 -0               ; @r{The integer 0.}
 @end example
@@ -195,7 +196,7 @@ point values:
 @samp{1.0e+INF}
 @item negative infinity
 @samp{-1.0e+INF}
-@item Not-a-number 
+@item Not-a-number
 @samp{0.0e+NaN} or @samp{-0.0e+NaN}.
 @end table