https://bugs.kde.org/show_bug.cgi?id=417187
Stefan Maksimovic <stefan.maksimo...@rt-rk.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #125692|0 |1
is obsolete| |
Attachment #125693|0 |1
is obsolete| |
--- Comment #12 from Stefan Maksimovic <stefan.maksimo...@rt-rk.com> ---
Created attachment 126210
--> https://bugs.kde.org/attachment.cgi?id=126210&action=edit
cdebug_zlib logs
An update regarding the proposed approach in the last comment:
We've modified the disInstr_MIPS_WRK function to recursively call itself
in case of a branch instruction.
This has proven itself to be effective, as valgrind now does speculate on
conditional branches which can be seen in the debug output (after the
[proposed solution pt 2] has been applied).
The branches and their delay slots get nicely bundled in a single
8-byte instruction.
This comprises the changes in the [proposed solution pt 1].
A few problems exist though, as there are a couple of tests failing across our
test machines. They appear after the [proposed solution pt 2] patch
has been applied, which enables the speculative execution.
As an example of that, we can take a look at memcheck/tests/cdebug_zlib (its
source, cdebug.c):
int main() {
int x;
if (x) return 1;
return 0;
}
In addition to the existing output in its stderr file, we now have an
additional
message:
Syscall param exit_group(status) contains uninitialised byte(s)
at 0x491A568: _Exit (_exit.c:32)
by 0x48A0E58: __run_exit_handlers (exit.c:97)
by 0x48A0ED8: exit (exit.c:104)
by 0x4881800: (below main) (libc-start.c:321)
We've analysed this for some time, but haven't been able to get to the bottom
of
where the new error originates from, nor do we observe any other architectures
experiencing this kind of failure.
The attached file includes the debug output of the cdebug_zlib test runs.
Any thoughts on this?
--
You are receiving this mail because:
You are watching all bug changes.
