Fix unit tests on i386 by forcing floats to doubles The unit tests check that various macros and number to string functions operate as expected. However on i386 the precision of the floating point numbers is not quite as expected, which leads to test failures. These are not seen on x86_64 or other platforms, but can be worked around by casting the numbers in questions to double precision rather than defaulting to floats. . See https://www.earth.li/~noodles/blog/2017/08/help-me-c.html and the associated comments for further details. diff --git a/tests/strutil.c b/tests/strutil.c index a36b6a2d..8883d85a 100644
tests: strutil, use ck_assert We pass no message, so use ck_assert instead of ck_assert_msg. This results in an error with check 0.15: tests/strutil.c:157:2: error: too few arguments to function '_ck_assert_failed' 157 | ck_assert_msg(saved_locale != NULL);
diff --git a/tests/strutil.c b/tests/strutil.c index fca70eaa..ec223332 100644
driver_list: unbreak list of builtin drivers for LTO configurations Check for the availability of the "no_reorder" linker attribute, which keeps the list of builtin drivers in shape on LTO enabled build setups. Keep backwards compatibility for platforms which lack support for the "no_reorder" attribute. Phrase the implementation such that other keywords as well as user provided external specs are possible.
