Gleb Fotengauer-Malinovskiy wrote:
> Following the glibc commit glibc-2.38~298 ("Mark various cold functions
> as __COLD"), the compilation of projects employing the manywarnings
> module (such as GNU grep) with with the -flto flag triggers a GCC
> warning:
>
> sigsegv.c: In function ‘stackoverflo
On CentOS 6 (glibc 2.12) I see this test failure:
FAIL: test-mbrtoc32-regular
===
../../gltests/test-mbrtoc32-regular.c:65: assertion 'mbsinit (&state)' failed
FAIL test-mbrtoc32-regular (exit status: 134)
This patch fixes it, in the same way as for newer glibc versions
The fnmatch() unit tests currently
- succeed on glibc versions >= 2.22 (here REPLACE_FNMATCH=0 and the glibc
fnmatch() is good enough),
- succeed on glibc versions < 2.13 (thanks to REPLACE_FNMATCH=1).
But for the versions in-between the behaviour is inconsistent: I see
test-fnmatch-[12].s
On Slackware 13.37, in a testdir, I see a number of test failures:
FAIL: test-c32isalnum.sh
../../gltests/test-c32isalnum.c:42: assertion 'ret == n' failed
../../gltests/test-c32isalnum.sh: line 40: 29713 Aborted
LC_ALL=$LOCALE_ZH_CN ${CHECKER} ./test-c3
Following the glibc commit glibc-2.38~298 ("Mark various cold functions
as __COLD"), the compilation of projects employing the manywarnings
module (such as GNU grep) with with the -flto flag triggers a GCC
warning:
sigsegv.c: In function ‘stackoverflow_deinstall_handler.part.0’:
sigsegv.c:1441:1:
I wrote:
> So, the test passes on all these platforms:
> - Linux: Ubuntu 22.04, Alpine Linux
> - Debian GNU/Hurd 2022
> - Debian GNU/kFreeBSD 7
> - NetBSD 9.3
> - OpenBSD 7.2
> - Cygwin 2.9.0
It passes also on Android 11, within the Termux app.
(I now got past the build failure.)
Brun