On Mon, Oct 30, 2017 at 09:01:25PM +0100, Kamil Rytarowski wrote:
> On 30.10.2017 08:24, Jakub Jelinek wrote:
> > On Thu, Oct 26, 2017 at 09:50:43PM +0200, Kamil Rytarowski wrote:
> >> $ make check-asan
> >> $ make check-asan-dynamic
> >> $ make check-ubsan
> >
> > That is testing of the upstream code, not of GCC and the libsanitizer
> > copy in GCC. What I'm more interested to hear is whether
> > you've bootstrapped/regtested the gcc tree with this patch on
> > x86_64-*-netbsd*, as per https://gcc.gnu.org/contribute.html
> > I.e. ..../configure ...; make -jN bootstrap; make -jN -k check;
> > ..../contrib/test_summary
> > and from there if there are any */asan/* or */ubsan/* FAILs.
> >
>
> I've been executing GCC tests.
>
> Some/many tests were hanging and I was killing them after a longer
> period of time. There were certainly environment issues, like attempts
> to execute non-existent 'python' (in pkgsrc/NetBSD we version python to
> python2.7, python3.6 etc).
>
> http://netbsd.org/~kamil/gcc/test_summary.log.8-20171022.txt
That seems that asan pretty much doesn't work at all in GCC for netbsd.
A few FAILs might be acceptable, but so many FAILs certainly aren't.
The testsuite doesn't use python, at least not for *san testing nor
test_summary, so that shouldn't be the problem. If it is asan/ubsan tests
that are hanging, that is something that needs to be debugged and understood
why it hangs.
You should look into ...objdir/gcc/testsuite/{gcc,g++}/{gcc,g++}.log
for details on some short/simple tests and see what the problem is.
Jakub
