|author||Iain Sandoe <email@example.com>||2021-12-31 11:52:22 +0000|
|committer||Iain Sandoe <firstname.lastname@example.org>||2021-12-31 13:16:16 +0000|
|parent||testsuite: XFAIL some Wstringop-overflow tests ... (diff)|
libgfortran: Fix bootstrap on targets without static_assert macro.
Although we build the library with GCC which is known to support _Static_assert this might be done on a system without the macro mapping static_assert to the compiler keyword. The use of static_assert introduced with r12-6126-g3430132f3e82 causes bootstrap to fail on such targets, fixed by using the keyword directly. Signed-off-by: Iain Sandoe <email@example.com> libgfortran/ChangeLog: * runtime/string.c (gfc_itoa): Use _Static_assert directly instead of via the static_assert macro.
Diffstat (limited to 'libgfortran')
1 files changed, 2 insertions, 2 deletions
|@@ -242,8 +242,8 @@ gfc_itoa (GFC_UINTEGER_LARGEST n, char *buffer, size_t len)|
|242||integers (we would need three calls), but they do suffice for all||242||integers (we would need three calls), but they do suffice for all|
|243||values up to 2^127, which is the largest that Fortran can produce||243||values up to 2^127, which is the largest that Fortran can produce|
|244||(-HUGE(0_16)-1) with its signed integer types. */||244||(-HUGE(0_16)-1) with its signed integer types. */|
|245||static_assert(sizeof(GFC_UINTEGER_LARGEST) <= 2 * sizeof(uint64_t),||245||_Static_assert (sizeof(GFC_UINTEGER_LARGEST) <= 2 * sizeof(uint64_t),|
|246||"integer too large");||246||"integer too large");|
|248||GFC_UINTEGER_LARGEST r;||248||GFC_UINTEGER_LARGEST r;|
|249||r = n % TEN19;||249||r = n % TEN19;|