u-boot.git/test/stdint/test-includes.sh, branch v2026.04 Unnamed repository; edit this file 'description' to name the repository. Remove CONFIG_USE_STDINT 2018-09-11T00:48:16+00:00 Masahiro Yamada yamada.masahiro@socionext.com 2018-08-06T11:47:38+00:00 9865543ae65d7c9a435eedfc6a0ba23efb291121 You do not need to use the typedefs provided by compiler. Our compilers are either IPL32 or LP64. Hence, U-Boot can/should always use int-ll64.h typedefs like Linux kernel, whatever the typedefs the compiler internally uses. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 
You do not need to use the typedefs provided by compiler.

Our compilers are either IPL32 or LP64.  Hence, U-Boot can/should
always use int-ll64.h typedefs like Linux kernel, whatever the
typedefs the compiler internally uses.

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
test: Add a simple test to detected warnings with uint64_t, uintptr_t 2014-10-27T15:04:01+00:00 Simon Glass sjg@chromium.org 2014-10-15T10:38:39+00:00 b01495e644db8315bd32b9e8d324487ef4f5b4f6 These types are problematic because they are typically declared in a non-standard way in U-Boot. For example, U-Boot uses 'long long' for int64_t even on a 64-bit machine whereas stdint.h uses 'long'. Similarly, U-Boot always uses 'long' for intptr_t whereas stdint.h mostly uses 'int'. This simple test script runs a few toolchains on a few archs to check for warnings. Signed-off-by: Simon Glass <sjg@chromium.org> 
These types are problematic because they are typically declared in a
non-standard way in U-Boot. For example, U-Boot uses 'long long' for
int64_t even on a 64-bit machine whereas stdint.h uses 'long'.
Similarly, U-Boot always uses 'long' for intptr_t whereas stdint.h mostly
uses 'int'.

This simple test script runs a few toolchains on a few archs to check for
warnings.

Signed-off-by: Simon Glass <sjg@chromium.org>