[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-18 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=417281 Andreas Arnez changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-18 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #9 from Andreas Arnez --- (In reply to Julian Seward from comment #8) > For the NEVER case, it might be more "symmetrical" in relation to > the ALWAYS case, to say that it modifies dst, rather than saying > nothing. (I know it modifies it

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-18 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #8 from Julian Seward --- (In reply to Andreas Arnez from comment #7) > Created attachment 126871 [details] > s390x: Fix register usage of conditional moves Looks good to me. Two minor points: For the NEVER case, it might be more

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-18 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #7 from Andreas Arnez --- Created attachment 126871 --> https://bugs.kde.org/attachment.cgi?id=126871=edit s390x: Fix register usage of conditional moves -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #6 from Julian Seward --- Created attachment 126754 --> https://bugs.kde.org/attachment.cgi?id=126754=edit Longer disassembly for comment 5 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #5 from Julian Seward --- (In reply to Julian Seward from comment #4) > As a next step I am inclined to add printf lines for all cases (rules) > in the insn selector. Then run the test case with and without &&-recovery > enabled, so as to

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-03-09 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #4 from Julian Seward --- I studied this more today. One theory I had was that the insn selector was generating wrong code for converting a value in the lowest bit of a register into a condition code (function s390_isel_cc(), case "/*

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-02-07 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #3 from Andreas Arnez --- Created attachment 125752 --> https://bugs.kde.org/attachment.cgi?id=125752=edit Excerpt of Valgrind output with --trace-flags=1000 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-02-07 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #2 from Andreas Arnez --- Created attachment 125751 --> https://bugs.kde.org/attachment.cgi?id=125751=edit Patch to enable "grail" on s390x -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 417281] s390x: /bin/true segfaults with "grail" enabled

2020-02-07 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=417281 --- Comment #1 from Andreas Arnez --- The crash happens in glibc's elf/dl-lookup.c in do_lookup_x, when trying to access the first element of the array 'list'. It seems that the register containing the address is corrupted; it was just copied from %r4