Commit 2783096f authored by Akira Yokosawa's avatar Akira Yokosawa Committed by Jonathan Corbet
Browse files

docs: submit-checklist: Expand on build tests against different word sizes



Existing sentence on cross-compilation that mentions ppc64 does not
make much sense in today's perspective.

Expand it for the benefits of testing against architectures of
different word sizes and endianness.

Signed-off-by: default avatarAkira Yokosawa <akiyks@gmail.com>
Reviewed-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/05c0b99c-c2e9-4702-90fd-8a4127586424@gmail.com
parent 07ab93f3
Loading
Loading
Loading
Loading
+6 −3
Original line number Diff line number Diff line
@@ -91,9 +91,12 @@ Build your code
     fix any issues.

2) Builds on multiple CPU architectures by using local cross-compile tools
   or some other build farm. Note that ppc64 is a good architecture for
   cross-compilation checking because it tends to use ``unsigned long`` for
   64-bit quantities.
   or some other build farm.
   Note that testing against architectures of different word sizes
   (32- and 64-bit) and different endianness (big- and little-) is effective
   in catching various portability issues due to false assumptions on
   representable quantity range, data alignment, or endianness, among
   others.

3) Newly-added code has been compiled with ``gcc -W`` (use
   ``make KCFLAGS=-W``).  This will generate lots of noise, but is good