2020-12-06 Paul Eggert <eggert@cs.ucla.edu>
+ doc: fix flat address space discussion
+ * doc/gnulib-readme.texi (Other portability assumptions):
+ Move the all-bits-zero assumption outside the flat address space
+ section, since the two issues are independent.
+
doc: document -static-libubsan more
* doc/gnulib-readme.texi (High Quality): Document pros and cons of
-static-libubsan a bit more. Mostly cons.
In particular, an unsigned type and its signed counterpart have the
same number of bits when you count the latter's sign bit.
+@item
+Objects with all bits zero are treated as 0 or NULL@. For example,
+@code{memset@ (A, 0, sizeof@ A)} initializes an array @code{A} of
+pointers to NULL.
+
@item
The types @code{intptr_t} and @code{uintptr_t} exist, and pointers
can be converted to and from these types without loss of information.
into @var{T} bytes, which can't happen in realistic flat-address-space
hosts.
-@item
-Objects with all bits zero are treated as 0 or NULL@. For example,
-@code{memset@ (A, 0, sizeof@ A)} initializes an array @code{A} of
-pointers to NULL.
-
@item
Adding zero to a null pointer does not change the pointer.
For example, @code{0 + (char *) NULL == (char *) NULL}.