https://bugs.kde.org/show_bug.cgi?id=486180
--- Comment #8 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #7)
> The current use only really is known to work for s390x.
The use for the extension mechanism, yes. But I was under the impression that
this field is required for
https://bugs.kde.org/show_bug.cgi?id=450705
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=450705
--- Comment #7 from Andreas Arnez ---
(In reply to Andreas Arnez from comment #6)
> Created attachment 168623 [details]
> Updated version of the extension proposal
I pushed this now, as a preparation to adding NNPA support. If there are sti
https://bugs.kde.org/show_bug.cgi?id=450705
--- Comment #6 from Andreas Arnez ---
Created attachment 168623
--> https://bugs.kde.org/attachment.cgi?id=168623=edit
Updated version of the extension proposal
This updated version of the extension proposal addresses the following:
* Add a comm
https://bugs.kde.org/show_bug.cgi?id=450705
--- Comment #4 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #3)
> Extension idea was posted to the mailinglist:
> https://sourceforge.net/p/valgrind/mailman/message/58753610/
Right. I'd like to go ahead with this, if tha
https://bugs.kde.org/show_bug.cgi?id=465782
Andreas Arnez changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=472875
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=472875
--- Comment #4 from Andreas Arnez ---
Created attachment 160801
--> https://bugs.kde.org/attachment.cgi?id=160801=edit
Three-part patch series for fixing some issues in the dfp-1 and pfp test cases
This should fix the issue with the condition c
https://bugs.kde.org/show_bug.cgi?id=472875
--- Comment #3 from Andreas Arnez ---
(In reply to Miroslav Franc from comment #2)
> Created attachment 160744 [details]
> [...]
> I just tried it and it seems to work. But, if you already have a fix or
> better idea, feel free to ign
https://bugs.kde.org/show_bug.cgi?id=472875
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=470132
Andreas Arnez changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=470978
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=470978
--- Comment #3 from Andreas Arnez ---
Created attachment 159694
--> https://bugs.kde.org/attachment.cgi?id=159694=edit
Build with -Wl,--s390-pgste if the linker supports it
This patch should enable building with -Wl,--s390-pgste. I've tes
https://bugs.kde.org/show_bug.cgi?id=470978
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=471032
--- Comment #2 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #1)
> I don't fully understand the s390x assembly, but this fix looks correct to
> me.
> With the patch the code becomes:
>
> 1001286: 58 00 20 0
https://bugs.kde.org/show_bug.cgi?id=470978
Bug ID: 470978
Summary: s390x: Valgrind cannot start qemu-kvm when "sysctl
vm.allocate_pgste=0"
Classification: Developer tools
Product: valgrind
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=470132
--- Comment #2 from Andreas Arnez ---
Created attachment 159191
--> https://bugs.kde.org/attachment.cgi?id=159191=edit
Enhance test coverage for VGM
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470132
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=470132
--- Comment #1 from Andreas Arnez ---
Created attachment 159189
--> https://bugs.kde.org/attachment.cgi?id=159189=edit
Suggested fix for VGM
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470132
Bug ID: 470132
Summary: s390x: Assertion failure on VGM instruction
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=465782
--- Comment #2 from Andreas Arnez ---
(In reply to Andreas Arnez from comment #1)
> Created attachment 157848 [details]
> Enable compiling Valgrind with clang
I pushed the above. Now clang should compile Valgrind for s390x successfully,
https://bugs.kde.org/show_bug.cgi?id=465782
--- Comment #1 from Andreas Arnez ---
Created attachment 157848
--> https://bugs.kde.org/attachment.cgi?id=157848=edit
Enable compiling Valgrind with clang
This enables compiling Valgrind with Clang, excluding the s390-specific test
cases.
https://bugs.kde.org/show_bug.cgi?id=465782
Andreas Arnez changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=465782
Bug ID: 465782
Summary: s390x: Valgrind doesn't compile with Clang on s390x
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=460356
Andreas Arnez changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=460356
--- Comment #2 from Andreas Arnez ---
Created attachment 154601
--> https://bugs.kde.org/attachment.cgi?id=154601=edit
Patch with fixes and test cases
This patch series includes a fix for this issue. It also fixes the
implementation of some ot
https://bugs.kde.org/show_bug.cgi?id=460356
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=460356
Bug ID: 460356
Summary: s390: Sqrt32Fx4 -- cannot reduce tree
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=450705
--- Comment #2 from Andreas Arnez ---
Small update: I'm now considering a different approach that's more similar to
the way system calls are handled. Instead of calling a dirty helper, we would
have the dispatcher call a guest-specific extension
https://bugs.kde.org/show_bug.cgi?id=450705
Andreas Arnez changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=454040
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=454040
Andreas Arnez changed:
What|Removed |Added
Attachment #148994|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=454040
--- Comment #4 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #2)
> Looks good and fixes the issue for me.
> I think the for loop could/should be from i = 1. needle being zero sized
> (nlen == 0) and n[0] == h[0] (hh != n0) ha
https://bugs.kde.org/show_bug.cgi?id=454040
--- Comment #1 from Andreas Arnez ---
Created attachment 148994
--> https://bugs.kde.org/attachment.cgi?id=148994=edit
Add intercept for memmem on s390x
Add an intercept for memmem on s390x platforms. This fixes the problem in my
testing.
--
https://bugs.kde.org/show_bug.cgi?id=454040
Andreas Arnez changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=454040
Bug ID: 454040
Summary: s390x: False-positive memcheck:cond in memmem on
arch13 systems
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=450705
Bug ID: 450705
Summary: s390x: Add NNPA support (arch14)
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=444552
Andreas Arnez changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=447991
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=444552
--- Comment #3 from Andreas Arnez ---
Created attachment 146450
--> https://bugs.kde.org/attachment.cgi?id=146450=edit
Fix sys_ipc semtimedop for s390x
Apart from a potential glibc configuration problem, Valgrind should be fixed as
well.
https://bugs.kde.org/show_bug.cgi?id=444552
Andreas Arnez changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #5 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #4)
> OK, but does that mean that "vflr" isn't a real opcode because it doesn't
> define on what format it operates?
Basically yes. Well, strictly speaking,
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #3 from Andreas Arnez ---
(In reply to Jesus Checa from comment #2)
> ...
> Checking s390x opcodes, it feels like s390_irgen_VFLR is missing the case
> for when m3 == 0 (provided my inline asm is right).
Right, m3 == 0 is no
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #1 from Andreas Arnez ---
Created attachment 145141
--> https://bugs.kde.org/attachment.cgi?id=145141=edit
Fix VFLRX instruction
The problem was due to a typo in s390_irgen_VFLR. This fixes the typo.
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=447991
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=447991
Bug ID: 447991
Summary: s390x: Valgrind indicates illegal instruction on wflrx
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=81
Andreas Arnez changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=81
--- Comment #3 from Andreas Arnez ---
(In reply to Andreas Arnez from comment #2)
> [...] Note that this shouldn't
> affect the AUXV entry for the vDSO, which should still be removed from the
> AUXV.
Oops, that's not true. This version of
https://bugs.kde.org/show_bug.cgi?id=81
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=81
--- Comment #2 from Andreas Arnez ---
Created attachment 144394
--> https://bugs.kde.org/attachment.cgi?id=144394=edit
Keep vDSO mapping on s390x
In my testing this patch fixes the issue. Some other architectures already have
similar logic to k
https://bugs.kde.org/show_bug.cgi?id=81
Andreas Arnez changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=444242
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=95
--- Comment #3 from Andreas Arnez ---
Created attachment 142946
--> https://bugs.kde.org/attachment.cgi?id=142946=edit
Add -fno-builtin to the compile options for dhat/tests/copy
This patch avoids the issue by compiling the test case with -
https://bugs.kde.org/show_bug.cgi?id=95
Andreas Arnez changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=444242
Andreas Arnez changed:
What|Removed |Added
Attachment #142769|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=444242
--- Comment #1 from Andreas Arnez ---
Created attachment 142769
--> https://bugs.kde.org/attachment.cgi?id=142769=edit
Sign-extend "relative long" offset in EXRL
This fixes the calculation of the "relative long" address in
https://bugs.kde.org/show_bug.cgi?id=444242
Bug ID: 444242
Summary: s390x: Valgrind crashes on EXRL with negative offset
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=441474
Andreas Arnez changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=432387
Andreas Arnez changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=432387
--- Comment #8 from Andreas Arnez ---
(In reply to Peter Maydell from comment #7)
> It seems a bit confusing to me that a function named foo_assert() doesn't do
> an assert()...
Maybe. I'm open for suggestions for a better name. But since the
https://bugs.kde.org/show_bug.cgi?id=432387
--- Comment #6 from Andreas Arnez ---
(In reply to Julian Seward from comment #5)
> So .. am a bit unclear about this, but it doesn't matter. It's enough to
> say that it should be impossible to cause the front end to assert by feeding
> i
https://bugs.kde.org/show_bug.cgi?id=432387
--- Comment #4 from Andreas Arnez ---
(In reply to Julian Seward from comment #3)
> Nice work! The following look OK to land as-is:
> [...]
Great, thanks for reviewing!
> [...]
> Is `misc3` safe to always-build? Or would it re
https://bugs.kde.org/show_bug.cgi?id=432387
Andreas Arnez changed:
What|Removed |Added
Attachment #136581|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=434296
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=434296
Andreas Arnez changed:
What|Removed |Added
Attachment #138034|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=434296
--- Comment #6 from Andreas Arnez ---
(In reply to Julian Seward from comment #5)
> [...] I would suggest you do it for all of the
> insns covered by this bug, since they look like they could each generate
> 20 or more IRStmts per guest insn.
https://bugs.kde.org/show_bug.cgi?id=434296
--- Comment #4 from Andreas Arnez ---
(In reply to Julian Seward from comment #3)
> Is it possible for any incoming instruction to cause this assertion to
> fail?
Yes. Of course, only invalid code would do that.
> If so that should be
https://bugs.kde.org/show_bug.cgi?id=433863
Andreas Arnez changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=433863
--- Comment #5 from Andreas Arnez ---
(In reply to Julian Seward from comment #4)
> This seems reasonable to me.
Thanks! Applied as d74a637206ef5532ccd2ccb2e31ee2762f184e60.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434296
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=434296
--- Comment #2 from Andreas Arnez ---
Created attachment 138034
--> https://bugs.kde.org/attachment.cgi?id=138034=edit
Fix the memcheck false positives with s390x vector string insns
This patch set re-implements the IR transformation of all s3
https://bugs.kde.org/show_bug.cgi?id=433863
--- Comment #3 from Andreas Arnez ---
(In reply to Andreas Arnez from comment #2)
> Created attachment 137982 [details]
> Remove memcheck test cases for cs, cds, and csg
Any objections/comments? Otherwise I'm planning to apply the patch earl
https://bugs.kde.org/show_bug.cgi?id=433863
--- Comment #2 from Andreas Arnez ---
Created attachment 137982
--> https://bugs.kde.org/attachment.cgi?id=137982=edit
Remove memcheck test cases for cs, cds, and csg
This is the removal patch. Let me know if I'm missing something.
--
https://bugs.kde.org/show_bug.cgi?id=433863
--- Comment #1 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #0)
> After the fix some issues (in these tests) can no longer be detected. It is
> unclear if that can be fixed. So maybe these tests simply need to be deleted.
Rig
https://bugs.kde.org/show_bug.cgi?id=434296
Andreas Arnez changed:
What|Removed |Added
Summary|s390x: False-positive |s390x: False-positive
https://bugs.kde.org/show_bug.cgi?id=434296
--- Comment #1 from Andreas Arnez ---
As a heads up, I verified that all vector string instructions currently have
the potential to yield memcheck false positives. Thus I'm working on a fix
that re-implements all vector string instructions. Instead
https://bugs.kde.org/show_bug.cgi?id=430429
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=434296
Bug ID: 434296
Summary: s390x: False-positive memcheck diagnostics from VSTRC
instruction
Product: valgrind
Version: 3.15 SVN
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=432387
--- Comment #1 from Andreas Arnez ---
Created attachment 136581
--> https://bugs.kde.org/attachment.cgi?id=136581=edit
Support miscellaneous-instruction-extensions facility 3
This is the first part of arch13 (=z15) support. It adds supp
https://bugs.kde.org/show_bug.cgi?id=430429
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=433863
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
Status
https://bugs.kde.org/show_bug.cgi?id=430429
Andreas Arnez changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=432387
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
Status
https://bugs.kde.org/show_bug.cgi?id=432387
Bug ID: 432387
Summary: s390x: z15 instructions support
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=404076
Andreas Arnez changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=429864
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=429864
Andreas Arnez changed:
What|Removed |Added
Attachment #133842|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=429864
--- Comment #4 from Andreas Arnez ---
Created attachment 133881
--> https://bugs.kde.org/attachment.cgi?id=133881=edit
[v2] Fix memcheck false positives with compare-and-swap (CS)
This version includes the changes from before and u
https://bugs.kde.org/show_bug.cgi?id=429864
--- Comment #3 from Andreas Arnez ---
Created attachment 133842
--> https://bugs.kde.org/attachment.cgi?id=133842=edit
Fix memcheck false positives with compare-and-swap (CS)
Just as a preview, this is a first version of a fix. It only handles
https://bugs.kde.org/show_bug.cgi?id=404076
Andreas Arnez changed:
What|Removed |Added
Attachment #133812|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=404076
Andreas Arnez changed:
What|Removed |Added
Attachment #132244|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=404076
--- Comment #6 from Andreas Arnez ---
(In reply to Julian Seward from comment #5)
> Can you use simply IRExpr_Get(offset, Ity_F128) ? If you can, it would give
> better performance than doing the two F64 Gets and then joining the results
>
https://bugs.kde.org/show_bug.cgi?id=429864
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
Status
https://bugs.kde.org/show_bug.cgi?id=429864
Bug ID: 429864
Summary: s390x: C++ atomic test_and_set yields false-positive
memcheck diagnostics
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=428648
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=428648
--- Comment #2 from Andreas Arnez ---
Created attachment 132997
--> https://bugs.kde.org/attachment.cgi?id=132997=edit
Force 12-bit amode for vector loads
This should fix the issue.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=428648
--- Comment #1 from Andreas Arnez ---
Further analysis shows that the offending "load" originates from
s390_isel_vec_expr_wrk() while processing an Iex_Load. This function generates
the addressing mode with s390_isel_amode() and does
https://bugs.kde.org/show_bug.cgi?id=428648
Bug ID: 428648
Summary: s390_emit_load_mem panics due to 20-bit offset for
vector load
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=404076
Andreas Arnez changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=419503
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
1 - 100 of 273 matches
Mail list logo
