This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

What to do about all the gcc.dg/guality test failures?

I was wondering if something needs to be done about the gcc.dg/guality tests.

There are two main issues I see with these tests, one is that they are often
not run during testing and so failures do not show up.  I looked into this
and found that, at least on my ubuntu 16.04 system, the kernel parameter
kernel.yama.ptrace_scope is set to 1 by default.  This limits the use of
ptrace to direct child processes and causes the guality tests to not run
on my system.  They also don't show up as failures, all you get is a message
in the test log that says 'gdb: took too long to attach'.  After changing this
to 0, the guality tests do get run.

The second problem is that many of the tests fail when they are run.
For example, looking at some August test runs:

x86_64 failures:
aarch64 failures:
mips64 failures:
s390x failures:

These all show many failures in gcc.dg/guality.  Most of the failures
are related to using the '-O2 -flto' or '-O3' options.  If I remove those
option runs I get 15 failures involving 5 tests on my aarch64 system:


So I guess there are number of questions:  Are these tests worth runnning?
Do they make sense with -O3 and/or -O2 -flto?   If they make sense and 
should be run do we need to fix GCC to clean up the failures?  Or should
we continue to just ignore them?

Steve Ellcey

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]