[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-02-06 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=416301 Andreas Arnez changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-30 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=416301 Andreas Arnez changed: What|Removed |Added Attachment #125487|0 |1 is obsolete|

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-30 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416301 --- Comment #7 from Mark Wielaard --- Test with the revised patch look good. There are a couple of failures, but none seem related to this issue: == 746 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 2 post failure

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-30 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416301 --- Comment #6 from Mark Wielaard --- Created attachment 125541 --> https://bugs.kde.org/attachment.cgi?id=125541&action=edit updated patch with IROp cmp_op argument for s390_irgen_CxB () Testing this updated patch that adds an IrOp cmp_op argument t

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-30 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416301 --- Comment #5 from Mark Wielaard --- (In reply to Mark Wielaard from comment #4) > I tried the patch on koji (remote builder) on Fedora rawhide with GCC10. It > seems to cause: > > op name: CmpF32 > op type is (F32,F32) -> I32 > arg tys are (F64,F64

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-30 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416301 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #4 from Mark Wielaar

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-28 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=416301 Andreas Arnez changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-27 Thread Andreas Arnez
https://bugs.kde.org/show_bug.cgi?id=416301 --- Comment #2 from Andreas Arnez --- (In reply to Julian Seward from comment #1) > Andreas, given that newer GCC and LLVM do emit these now, it sounds like > supporting them is potentially of high priority. What's your view? Absolutely. I have a patc

[valgrind] [Bug 416301] s390x: "compare and signal" not supported

2020-01-22 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=416301 --- Comment #1 from Julian Seward --- Andreas, given that newer GCC and LLVM do emit these now, it sounds like supporting them is potentially of high priority. What's your view? -- You are receiving this mail because: You are watching all bug changes