458e2ed133
Each GCC target backend is at liberty to define its own SIZE_TYPE. GCC uses this for various purposes, not lease it drives the machinery that spits out format specifier diagnostics when format specifiers are applied to objects with inappropriate type. GCC exposes the current definition of SIZE_TYPE via the preprocessor symbol __SIZE_TYPE__. The GCC build processes also generates various standard library header files that directyle expose stanard types in a form consistent with the current configuration of GCC. Conventionally standard library build processes (for glibc and newlib) pick up the header files generated by the GCC build. In the minimal libc we have no such build process, we don't pick up the header files that the GCC build process generated. Instead we define our own alternative header files and align them with GCC manually. The current definition of ssize_t in minimal libc is out of step with GCC which means that any use of the %z[du] format modifier will issue a diagnostic. We replace the open coded architecture detection in minimal libc and use GCCs __SIZE_TYPE__ directly. Change-Id: I63b5e17bee4f4ab83d49e492e58efd3bafe76807 Signed-off-by: Marcus Shawcroft <marcus.shawcroft@arm.com> tests: fs: Fix printf warning when using newlib Current code uses %ld format specifier to print data of type ssize_t. This causes type warnings when built with newlib. The correct format specifier to be used for ssize_t is %zd. Change-Id: I02a3c628e3d6e8a36a09cd694220406d8faf1730 Signed-off-by: Ramesh Thomas <ramesh.thomas@intel.com> |
||
|---|---|---|
| .. | ||
| fat_fs | ||