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

--- Comment #33 from Paul Floyd <pa...@free.fr> ---
Over 10 years since this item was opened and it's my turn to take a stab at
getting it done.

Here a couple of sample results (best and worst)

GCC on amd64 configured with -O0
== 714 tests, 19 stderr failures, 5 stdout failures, 1 stderrB failure, 3
stdoutB failures, 0 post failures ==

clang on x86
== 648 tests, 69 stderr failures, 4 stdout failures, 4 stderrB failures, 4
stdoutB failures, 1 post failure ==


Stuff that's been fixed
~~~~~~~~~~~~~~~~~~~~~~~
FreeBSD 11.1 added a ~64MB MAP_GUARD region below the user stack which was
breaking the address space manager on x86.
For x86 on amd64 there was a failure arising from Valgrind not fully
synthesizing auxv for the guest combined with a bug in rtld. That took a long
time to hunt down.
x86 sigreturn was broken.
Debug output never worked on x86 and caused crashes on amd64.
There were several redir errors in drd and helgrind.
Added ~ 20 syscalls.


Remaining problems
~~~~~~~~~~~~~~~~~~
The number one remaining issue is with signal delivery, and it's worse on x86.

Some of the clang failures that I've looked at are due to the codegen. In a
couple of cases I saw that clang used cmov opcodes rather then test/jmp used by
GCC. I need to look ore at things like varinfo differences.

The default suppression file is pretty noisy with plain old libc functions. If
I run 'ps' under memcheck then I get a bunch of 'Conditional jumps' in strlen
and strvis. Qt apps could also do with some attention.


Not enough regtests yet. I've only added 7 I think. I definitely need to add a
'scalar' test.

Other stuff
~~~~~~~~~~~
There are a few other issues, but I might be able to live with them as known
limitations.

I've tried to clean out the diffs in common source files as much as possible,
but there's still some work to do. I have been fairly heavy handed in modifying
test scripts that use sed, and should probably make .in files and a configure
time AC_CONF_SED.

Next steps
~~~~~~~~~~
Before any talk of patches or code reviews:

I'd like to deal with the signal issues on x86, but that does not look easy.

The issues with clang need to be all analyzed, since this is the system
compiler.

Test, test, test.

My github repo is here
https://github.com/paulfloyd/freebsd_valgrind

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

Reply via email to