switch to init_arrray causes glibc testsuite failures
vineetgarc opened this issue · 1 comments
As part of glibc upstreaming, there was a request to get rid of custom crti/crtn and switch to generic init_array
http://lists.infradead.org/pipermail/linux-snps-arc/2018-December/005086.html
The corresponding change was ef7a0a0 and while it seemed to work, it causes a bunhc of tests to start failing.
FAIL: dlfcn/bug-atexit1
FAIL: dlfcn/bug-atexit2
FAIL: dlfcn/tstatexit
FAIL: dlfcn/tstcxaatexit
...
This needs to be checked.
The issue was gcc not being configured with init_array support, as the autoconf test was flawed - it only works for NON cross compilation setup.
https://sourceware.org/ml/libc-alpha/2019-01/msg00656.html
The fix was to enable this unconditionally in gcc for ARC.
http://lists.infradead.org/pipermail/linux-snps-arc/2019-January/005318.html
gcc patch has been merged into upstream (and also backported to gcc-8)
master : 2019-01-28 9ac27d8a65e9 [ARC]: Enable init_array support
gcc-8-stable: 2019-01-29 0d5ba57508c5 Backport ARC patches.
Test runs with this gcc restore back the results.