https://bugs.kde.org/show_bug.cgi?id=294285
Patrick J. LoPresti changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #84 from Patrick J. LoPresti ---
(In reply to Sam James from comment #79)
> Are Tanya's patches still pending review? Is there an outstanding known
> issue with them?
Similar question... What are the outstanding tasks here,
https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #65 from Patrick J. LoPresti ---
(In reply to Tanya from comment #64)
>
> If you would make the patch into a new branch - would you be interested in
> its internal commit history, perhaps for git blame?
I am not a Valgrind main
https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #63 from Patrick J. LoPresti ---
Could someone please work on getting these changes into mainline? Or at least
make this a branch in the git repository? (Is there anything I can do to help?)
AVX-512 is now a "must have" for us
https://bugs.kde.org/show_bug.cgi?id=383010
--- Comment #35 from Patrick J. LoPresti ---
(In reply to Tanya from comment #34)
Nice to see work resuming on this.
Valgrind is almost useless for us at this point, because AVX-512 CPUs are now
ubiquitous and the performance benefits are too large
https://bugs.kde.org/show_bug.cgi?id=404272
Patrick J. LoPresti changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=404272
--- Comment #2 from Patrick J. LoPresti ---
Should I try to put together a test case?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404272
Bug ID: 404272
Summary: vex amd64->IR: unhandled instruction bytes: 0x66 0xF
0x38 0x23 0xC0 0xF3 (PMOVSXWD)
Product: valgrind
Version: 3.15 SVN
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=383010
Patrick J. LoPresti changed:
What|Removed |Added
CC||lopre...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=371989
--- Comment #5 from Patrick J. LoPresti ---
Just a thought... How about adding VEX opcodes corresponding to these string
instructions?
Although the behavior of these instructions is (ludicrously) complex, the data
flow is pretty simple: Two vectors of
https://bugs.kde.org/show_bug.cgi?id=372358
Patrick J. LoPresti changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=372358
--- Comment #3 from Patrick J. LoPresti ---
Well, that is weird... I am not making it up :-)
I was using the 3.12.0 release. Is it possible this has been fixed in SVN?
I will check, but probably not until next week. Thanks, Julian
--
You are
https://bugs.kde.org/show_bug.cgi?id=372358
--- Comment #1 from Patrick J. LoPresti ---
I meant "GDB" not "GCC" obviously.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372358
Bug ID: 372358
Summary: vex amd64->IR: unhandled instruction bytes: 0xC5 0xFA
0x7F 0x45 0x80 0xC5 0xFA 0x7F 0x4D 0x90
Product: valgrind
Version: 3.12 SVN
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=371989
--- Comment #3 from Patrick J. LoPresti ---
Created attachment 101986
--> https://bugs.kde.org/attachment.cgi?id=101986&action=edit
Test case illustrating pcmpistri $0x12 validity bit propagation failure
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=371989
--- Comment #2 from Patrick J. LoPresti ---
A similar problem happens with Intel's optimized atoi() routine. Actually this
is so similar that I believe these can probably be fixed together, so I am just
adding the second test case to this bug repo
https://bugs.kde.org/show_bug.cgi?id=371989
Patrick J. LoPresti changed:
What|Removed |Added
Summary|PCMPISTRM $0x72 validity|PCMPISTRM $0x72 and
https://bugs.kde.org/show_bug.cgi?id=371989
--- Comment #1 from Patrick J. LoPresti ---
Forgot to mention:
I believe this example should run without warnings when "--partial-loads-ok=yes
--expensive-definedness-checks=yes" are specified to memcheck.
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=371989
Bug ID: 371989
Summary: PCMPISTRM $0x72 validity bit propagation is imprecise
Product: valgrind
Version: 3.12 SVN
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
19 matches
Mail list logo
