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: Akira Yokosawa <akiyks@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/05c0b99c-c2e9-4702-90fd-8a4127586424@gmail.com
This commit is contained in:
Akira Yokosawa 2025-01-30 16:28:09 +09:00 committed by Jonathan Corbet
parent 07ab93f3cc
commit 2783096fb1

View File

@ -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