https://bugs.kde.org/show_bug.cgi?id=208531

--- Comment #34 from Paul Floyd <pa...@free.fr> ---
Some gory details, part 1. In the FreeBSD world, normally there are 2 active
release streams (currently 11 and 12) and one development stream (currently
13). The system compiler is clang, with GCC as an optional install. Whilst
other architectures are supported by FreeBSD, amd64 and x86 are the only two
that work with Valgrind. x86 (i386 in the FreeBSD world) is still fairly widely
used.

My primary build/test work is all on FreeBSD 12.1. I started with amd64/GCC but
 now I'm concentrating on amd64/clang. I also build and test on x86/clang and
x86/gcc. I occasionally do builds on FreeBSD 11.3.

Here are some regtest results that I'm currently getting, and some analysis of
the failures.

More analysis here https://github.com/paulfloyd/freebsd_valgrind/issues

amd64/clang
== 725 tests, 22 stderr failures, 1 stdout failure, 1 stderrB failure, 0
stdoutB failures, 0 post failures ==


memcheck/tests/leak* (4 fails)
There's a discrepancy with clang between the client request report and the
final report. WIP.

drd/tests/omp (3 fails)
Many errors, not fully analysed. clang support for OpenMP seems fairly weak.

memcheck/tests/varinfo6 (+1 similar)
drd/tests/tc04_free_lock
Issue with getting varinfo, error line number printed as 0

drd/tests/dlopen
Hits an assert setting pthreadid, possibly related to the special handling that
was required for dlopen on Solaris.

memcheck/tests/descr_belowsp
Error message doesn't mention guard page. Needs different guard page detection
heuristics?

memcheck/tests/gone_abrt_xml
helgrind/tests/tc22_exit_w_lock 
There's a hack for stacktraces without function call prologs that doesn't work
in these 2 cases.

gdbserver_tests/mcinfcallWSRU
Line number diffs in stderrB. Looks harmless.

memcheck/tests/amd64/insn-pmovmskb
Looks like clang optimization won the day with this testcase. Missing error
messages and changes in order.

memcheck/tests/clientperm
Looks like clang optimization of branches.

helgrind/tests/tls_threads (+ drd)
Hard problem. On Linux this relies on spying on libc variables for tls. That
doesn't work with non-GCC FreeBSD libc.

helgrind/tests/pth_cond_destroy_busy
One missing error message

helgrind/tests/tc22_exit_w_lock 

drd/tests/std_list
A load of locale errors.

drd/tests/atomic_var
Missing varinfo details

none/tests/amd64/ssse3_misaligned
SIGSEGV in host :-(

none/tests/rlimit_nofile
Only fails when I'm on KDE because of an extra krunner socket.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to