https://bugs.kde.org/show_bug.cgi?id=444545
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #16 from Peter Hull ---
(In reply to Paul Floyd from comment #15)
> Did the VBox CPU change in any ways (different lscpu flags)?
Yes, it has changed, avx and avx2 have gone, and bmi1 and bmi2 have appeared,
together with some other changes (
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #15 from Paul Floyd ---
Did the VBox CPU change in any ways (different lscpu flags)?
Not much has changed in Valgrind. I did make one change that affects hwcaps and
the CPUID dirtyhelper, but I don't think that is relevant.
Is BMI support
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #14 from Peter Hull ---
It does seem to have been fixed for me now, running under VirtualBox 7.0.8:
glibc.x86_64 2.37-4.fc38
gcc version 13.1.1 20230426 (Red Hat 13.1.1-1)
valgrind-3.21.0
Fedora 38 6.2.13-300.fc38.x86_64
I don't know which
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #13 from Peter Hull ---
Christopher, that's really interesting and it sounds like you have found the
cause. From my point of view I have been checking (very infrequently) to see if
some update to Fedora or VirtualBox has magically fixed it..
https://bugs.kde.org/show_bug.cgi?id=444545
Christopher Wecht changed:
What|Removed |Added
CC||cwe...@mailbox.org
--- Comment #12 from Chr
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #11 from Peter Hull ---
(In reply to Julian Seward from comment #10)
> Q: for the failing case, does
> adding `--alignment=32` make any difference?
That didn't make any difference that I could see.
I found that running it like this:
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #10 from Julian Seward ---
That is all very strange. Q: for the failing case, does
adding `--alignment=32` make any difference? That changes
the alignment produced by `malloc`.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #9 from Peter Hull ---
Created attachment 143101
--> https://bugs.kde.org/attachment.cgi?id=143101&action=edit
Updated/simplified test case
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #8 from Peter Hull ---
I did a little more checking. I reduced the test program somewhat (attached)
I tried putting a breakpoint on memchr both standalone and running under
valgrind, to see what got called. I saw for 'standalone'
(gdb) run
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #7 from Peter Hull ---
As I'm using VirtualBox I can restart the VM with AVX2 disabled, using the
command
.\vboxmanage setextradata "Fedora" VBoxInternal/CPUM/IsaExts/AVX2 0
Now the problem does not occur.
However, I did report in comment
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #6 from Julian Seward ---
> Model name:Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Hmm, nothing particularly exotic there.
> Sorry this is proving more troublesome than I expected.
It's OK; however; we can't fix it if we can't r
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #5 from Peter Hull ---
Sorry this is proving more troublesome than I expected.
$ lscpu
Architecture:x86_64
CPU op-mode(s):32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order:
https://bugs.kde.org/show_bug.cgi?id=444545
Julian Seward changed:
What|Removed |Added
CC||jsew...@acm.org
--- Comment #4 from Julian Sewa
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #3 from Peter Hull ---
I still get the problem on Fedora 35, gcc 11.2.1, valgrind from current (as of
today) git (Valgrind-3.19.0.GIT)
Suggests that gcc 11 is miscompiling something?
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #2 from Peter Hull ---
(I should add I was running in a virtualbox vm if that is significant?)
It is also OK under Debian, which has gcc version 10.2.1 20210110 (Debian
10.2.1-6) and Valgrind-3.16.1
On Fedora, where it shows the problem,
https://bugs.kde.org/show_bug.cgi?id=444545
--- Comment #1 from Paul Floyd ---
I can't reproduce this (GCC 5.3 and 9.2 on RHEL 7.6, Valgrind built from git
source).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444545
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this mail
18 matches
Mail list logo