https://bugs.kde.org/show_bug.cgi?id=490520
--- Comment #3 from Paul Floyd ---
I've been using LLVM compilers for several years without any issues.
Are you seeing configure passing this test:
# does the x86/amd64 assembler understand the LOOPNEL instruction?
# Note, this doesn't generate a C
https://bugs.kde.org/show_bug.cgi?id=490520
Paul Floyd changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=490520
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=490182
--- Comment #2 from Paul Floyd ---
That's probably this bit
case HRcVec128: {
HReg x21 = hregARM64_X21(); // baseblock
HReg x9 = hregARM64_X9(); // spill temporary
vassert(0 == (offsetB & 15)); // check
https://bugs.kde.org/show_bug.cgi?id=490182
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=391311
--- Comment #2 from Paul Floyd ---
Other than the
+#if defined(__ARM_FEATURE_CRYPTO)
bits all these have been addressed (and sime without using clang conditional
blocks).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391311
--- Comment #1 from Paul Floyd ---
I may well have reinvented this wheel with the port to FreeBSD arm64, which
also uses the LLVM toolchain.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391311
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
CC
https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #10 from Paul Floyd ---
I have some credits on AWS, so I could probably test it there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=476465
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=255494
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=317127
Paul Floyd changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=489707
--- Comment #1 from Paul Floyd ---
First, are you certain that it was only the change from Valgrind 3.18.1 to
Valgrind 3.23 that caused the change?
I just checked out the code for 3.18.1 and using GCC 14.1 on RHEL 7..6 I get
the same error with both
https://bugs.kde.org/show_bug.cgi?id=489707
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #20 from Paul Floyd ---
And regtest results
== 737 tests, 6 stderr failures, 2 stdout failures, 0 stderrB failures, 1
stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls(stdoutB)
memcheck/tests/pointer-trace
https://bugs.kde.org/show_bug.cgi?id=489221
Paul Floyd changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=489221
--- Comment #7 from Paul Floyd ---
Is it OK to close this item then?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489338
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=489338
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=489221
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=383010
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=79787
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=226105
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=391148
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=417572
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=381326
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #12 from Paul
https://bugs.kde.org/show_bug.cgi?id=489088
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #18 from Paul Floyd ---
On a machine that is StarFive JH7100 SoC (2x SiFive U74 at 1.20 GHz)
I have a problem with make check.
gcc -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -o
compressed compressed.o
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #17 from Paul Floyd ---
On amd64 Linux, one warning that I've opened an issue for on Petr's github.
A few other warnings about pointer-to-int-casts.
regtest clean.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488715
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=460951
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #16 from Paul Floyd ---
I think it's a regression that I added. Should be fixed. I'll check again when
Petr rebases next, and I'll also give Linux amd64 a go and see if I can build
and run regtest on riscv.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #14 from Paul Floyd ---
I built and ran regtest on my github clone of
https://github.com/petrpavlu/valgrind-riscv64 on FreeBSD amd64.
There were a couple of unexpected failures in memcheck/tests/freebsd (one of
the scalars and eventfd2
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #18 from Paul Floyd ---
commit c19d19d34a6dadaf4a9d590f516f813e9cbacdd0
Author: Paul Floyd
Date: Sun Jun 16 09:25:51 2024 +0200
Bug 487439 - SIGILL in JDK11, JDK17
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=488514
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=488514
--- Comment #3 from Paul Floyd ---
As a workaround, if you target something like ARM8.2 (-march=armv8.2 maybe)
then does it work?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488514
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #19 from Paul Floyd ---
(In reply to Olly Betts from comment #18)
> I'm using valgrind via a testsuite harness and valgrind's output unhelpfully
> gets interleaved with other output so it was much much easier to just cut
>
https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #17 from Paul Floyd ---
This is getting frustrating.
I keep asking questions and you keep (incorrectly) second guessing something
else.
I'm still waiting to see the exact error. I don't want you to second guess that
it means just the top
https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #15 from Paul Floyd ---
Also in your libc, is there more than one function using the same address as
__memmove_chk? (And specifically, is __memcpy_chk the same as __memmove_chk).
First do something like
nm -D /lib/libc.so.7 | grep
https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #14 from Paul Floyd ---
(In reply to Olly Betts from comment #13)
> ==4137856== Source and destination overlap in memcpy_chk(0x1ffeffb000,
> 0x1ffeffb010, 10224)
> ==4137856==at 0x484BE22: __memcpy_chk (in
> /usr/libe
https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #12 from Paul Floyd ---
Adding a suppression is probably not the answer. Running under memcheck there
shouldn't even be a call to __memcpy_chk from memmove.
The question is why Valgrind isn't rediecting the call to memmove? On Linux
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #15 from Paul Floyd ---
Do you have any way of telling which compiler was used to produce the binary
that is generating sigill?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488169
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #7 from Paul Floyd ---
As to implementing this, my idea is to add a new variable VG_(brk_high_tide)
that starts off the same as VG_(brk_limit),
If ever VG_(brk_limit) is increased beyond VG_(brk_high_tide) then a new
VG_
https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #3 from Paul Floyd ---
(In reply to John Reiser from comment #2)
> (In reply to Paul Floyd from comment #1)
> > brk() is fairly old, removed from posix accordingly to the Linux manpage.
> > Increasingly I see it getti
https://bugs.kde.org/show_bug.cgi?id=487439
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487862
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487993
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=487993
--- Comment #6 from Paul Floyd ---
I think that I see the cause.
https://elixir.bootlin.com/glibc/glibc-2.37/source/sysdeps/i386/malloc-alignment.h#L22
GNU libc has a special case for x86 bumping up the alignment to 16 bytes.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=488026
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=488026
--- Comment #4 from Paul Floyd ---
FreeBSD and Darwin also need changes. I'll close this when I've done them.
commit ecd6d353a5ec2fd12665947235186ab014b629e8 (HEAD -> master, origin/master,
origin/HEAD)
Author: Ethiraric
Date: Tue Jun 4 18:37
https://bugs.kde.org/show_bug.cgi?id=488026
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=488026
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #3 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=487993
--- Comment #5 from Paul Floyd ---
I also get the assert on Fedora 40.
As a workaround you can use "--alignment=16".
However, I still don't quite understand what is happening. The operator new
that gets called is just plain bog standard op
https://bugs.kde.org/show_bug.cgi?id=487993
--- Comment #3 from Paul Floyd ---
^^^
clang++ 16.0.6
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487993
--- Comment #2 from Paul Floyd ---
And I just tried with Valgrind 3.23 and git HEAD on FreeBSD 14.0 amd64 16.0.6
and it works OK.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487993
--- Comment #1 from Paul Floyd ---
Can you try with the latest Valgrind? There have been a lot of changes to
aligned allocators and deallocators, mainly in Valgrind 3.22.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487993
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
CC
https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #1 from Paul Floyd ---
brk() is fairly old, removed from posix accordingly to the Linux manpage.
Increasingly I see it getting removed from platforms.
Nevertheless, I just downloaded a copy of SUSv1, and indeed it does say
The brk
https://bugs.kde.org/show_bug.cgi?id=487862
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #14 from Paul Floyd ---
(In reply to Bill Torpey from comment #13)
> Been testing for the past couple days, and it appears that the patch from
> https://bugs.kde.org/show_bug.cgi?id=487439#c10 is working fine for us --
> than
https://bugs.kde.org/show_bug.cgi?id=398569
Paul Floyd changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #11 from Paul Floyd ---
That doesn't work with clang unfortunately and I have to resort to the byte
array.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #9 from Paul Floyd ---
Bill Torpey, could you build Valgrind to test a fix?
This change seems to fix your problem:
diff --git a/VEX/priv/guest_amd64_toIR.c b/VEX/priv/guest_amd64_toIR.c
index f0b1c5516..28c37f092 100644
--- a/VEX/priv
https://bugs.kde.org/show_bug.cgi?id=453044
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=439082
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #4 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #7 from Paul Floyd ---
That's not unusual. There may be some kind of runtime instruction set selection
based on hwcaps/cpuid.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #5 from Paul Floyd ---
This looks like
66 48 0f 73 f1 0c rex.W psllq xmm1,0xc
Some more from the log
vex amd64->IR: unhandled instruction bytes: 0x66 0x48 0xF 0x73 0xF1 0xC 0x66
0xF 0x70 0xF5
vex amd64->IR: REX=1 REX.W=1 REX.R=0 R
https://bugs.kde.org/show_bug.cgi?id=487439
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=487418
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487418
Bug ID: 487418
Summary: [arm64] Cleanup M{SR,RS} instructions
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: FreeBSD
Status:
https://bugs.kde.org/show_bug.cgi?id=487410
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487410
Paul Floyd changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=487413
Paul Floyd changed:
What|Removed |Added
Summary|[arm64] Unhandled M{SR,RS} |[arm64] Unhandled M{SR,RS
https://bugs.kde.org/show_bug.cgi?id=487413
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487413
Bug ID: 487413
Summary: [arm64] Unhandled M{SR,RS} instructions and cleanup
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: FreeBSD
https://bugs.kde.org/show_bug.cgi?id=447989
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=453044
--- Comment #5 from Paul Floyd ---
glibc 2.28 I meant
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453044
--- Comment #4 from Paul Floyd ---
(In reply to Jesus Checa from comment #3)
> (In reply to Paul Floyd from comment #2)
> > Which version of gdb was this with?
>
> This was gdb 8.2
I just tried building gdb and couldn't reproduc
https://bugs.kde.org/show_bug.cgi?id=462958
Paul Floyd changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=447989
Paul Floyd changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=290061
--- Comment #6 from Paul Floyd ---
The patch no longer applies cleanly. Currently there is some special case code
for mips64. I've tried to access a suitable machine to check if this is still
relevant, but no success so far.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=447989
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=447989
--- Comment #13 from Paul Floyd ---
Thanks for the patches. I've applied, tested and pushed the first one. The
second patch looks OK so far but I'd like to check it on FreeBSD before pushing
the change. It might take me a little while to see if I can
https://bugs.kde.org/show_bug.cgi?id=290061
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew
https://bugs.kde.org/show_bug.cgi?id=487111
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=383010
Paul Floyd changed:
What|Removed |Added
CC||lefer...@gmail.com
--- Comment #96 from Paul
https://bugs.kde.org/show_bug.cgi?id=487124
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=411203
--- Comment #6 from Paul Floyd ---
It would probably be easiest to do this in valgrind itself. It already does
this to insert LD_PRELOADs for the core and tool vgpreaload libs.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447989
--- Comment #9 from Paul Floyd ---
(In reply to David Benjamin from comment #8)
> Regarding the generating the expected files by running the test, I assume
> those just record what my patch does. I.e. if my patch were wrong, the wrong
> thi
https://bugs.kde.org/show_bug.cgi?id=352021
--- Comment #8 from Paul Floyd ---
Still hanging. Need to look at is_signal_from_kernel to see if anything has
changed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447989
--- Comment #7 from Paul Floyd ---
(In reply to David Benjamin from comment #6)
> This was quite some time ago, so I'll have to page this back in and remind
> myself how I tested this. :-)
>
> > This will als
https://bugs.kde.org/show_bug.cgi?id=487055
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=487055
Paul Floyd changed:
What|Removed |Added
Summary|memcheck/tests/x86-linux/sc |memcheck/tests/x86-linux/sc
https://bugs.kde.org/show_bug.cgi?id=487055
--- Comment #2 from Paul Floyd ---
On second thoughts, just SUCC_OR_FAIL would be easier, but test a bit less.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=487055
--- Comment #1 from Paul Floyd ---
Out by one, it was 'nice' not 'ftime'. This patch works form me
--- a/memcheck/tests/x86-linux/scalar.c
+++ b/memcheck/tests/x86-linux/scalar.c
@@ -32,6 +32,11 @@ int main(void)
long x0 = px[0];
long res
https://bugs.kde.org/show_bug.cgi?id=487055
Bug ID: 487055
Summary: memcheck/tests/x86-linux/scalar fails runing in Docker
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Other
https://bugs.kde.org/show_bug.cgi?id=352021
--- Comment #7 from Paul Floyd ---
Can't easily try this on 10.10.
I'll have a go with a 10.13 VM.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352021
Paul Floyd changed:
What|Removed |Added
Assignee|rhysk...@gmail.com |pjfl...@wanadoo.fr
--
You are receiving
1 - 100 of 1609 matches
Mail list logo
