https://bugs.kde.org/show_bug.cgi?id=485487
Florian Weimer changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=501348
Bug ID: 501348
Summary: glibc built with -march=x86-64-v3 does not work due to
ld.so memcmp
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Ot
https://bugs.kde.org/show_bug.cgi?id=485487
--- Comment #8 from Florian Weimer ---
The ELN glibc scratch build succeeded:
https://src.fedoraproject.org/rpms/glibc/pull-request/92#comment-194579
There's a TMT failure, but it's unrelated (potential kernel robust mutex
issue). This tes
https://bugs.kde.org/show_bug.cgi?id=485487
--- Comment #4 from Florian Weimer ---
Based on a further suggestion from H.J., I put the strcmp implementation posted
here into glibc and ran its strcmp test suite against it. It passes. For such a
simple implementation it should have really good
https://bugs.kde.org/show_bug.cgi?id=485487
--- Comment #3 from Florian Weimer ---
H.J. suggests to use the implementation from
<https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/i386/i686/strcmp.S;h=e71d97f2a63a2d3c31e4c1be395c1a1f5e0200ff;hb=HEAD>
(adapted for x86-64). I can submi
https://bugs.kde.org/show_bug.cgi?id=485487
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=485487
Bug ID: 485487
Summary: glibc built with -march=x86-64-v3 does not work due to
ld.so strcmp
Classification: Developer tools
Product: valgrind
Version: 3.23 GIT
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=484002
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=462007
Bug ID: 462007
Summary: Implicit int in none/tests/faultstatus.c
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=434764
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=444552
--- Comment #5 from Florian Weimer ---
I think for several releases, glibc used the semtimedop system call by mistake:
it was only added to the kernel in Linux 5.1, so this led to compatibility
problems.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=449494
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=414268
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=442061
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=420906
--- Comment #4 from Florian Weimer ---
To reproduce, you can use Fedora rawhide (or 34) and install a glibc build on
top of it. https://koji.fedoraproject.org/koji/buildinfo?buildID=1782185 or any
build later than glibc-2.33.9000-44.fc35 will do
https://bugs.kde.org/show_bug.cgi?id=420906
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=431157
--- Comment #10 from Florian Weimer ---
What's the status here? The first glibc release with scv support is coming up.
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431157
--- Comment #9 from Florian Weimer ---
I think including the HTM bit is wrong, it should always be cleared along with
HTM_NOSC. I doubt valgrind supports HTM, so this ought to be the right thing to
do. It's definitely better than what we had b
https://bugs.kde.org/show_bug.cgi?id=431157
--- Comment #6 from Florian Weimer ---
Hmm. If we filter HTM_NOSC, we should also filter HTM.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431157
--- Comment #4 from Florian Weimer ---
Created attachment 134659
--> https://bugs.kde.org/attachment.cgi?id=134659&action=edit
0001-ppc64-Mask-unrecognized-AT_HWCAP2-values.patch
This is what I came up with.
It filters out DARN as well,
https://bugs.kde.org/show_bug.cgi?id=431157
--- Comment #2 from Florian Weimer ---
I think this does not work because the calling convention for “sc” and “scv 0”
are different.
The glibc test case misc/test-errno-linux is a good way to exercise syscall
errors. Here's how you can run it
https://bugs.kde.org/show_bug.cgi?id=431157
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=431157
Bug ID: 431157
Summary: PPC_FEATURE2_SCV needs to be masked in AT_HWCAP2
Product: valgrind
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=422683
--- Comment #1 from Florian Weimer ---
To clarify that the libc-alpha posting is not a proposal, it is a description
of the status quo.
The proposal (buried in there) is to move towards AT_HWCAP-based selection
exclusively, but that has not been
https://bugs.kde.org/show_bug.cgi?id=422683
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=408414
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--- Comment #1 from
https://bugs.kde.org/show_bug.cgi?id=406434
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=386945
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=396839
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #48 from Florian Weimer ---
With the current set of patches, I still see failures for the following glibc
string function tests:
string/test-memcmp
string/test-strcasecmp
string/test-strcmp
string/test-strncasecmp
string/test-strncmp
You
https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #39 from Florian Weimer ---
(In reply to Vadim Barkov from comment #38)
> (In reply to Florian Weimer from comment #30)
>
> Floarian,
>
> I can't reproduce the problem that you describe. Could you take my patch
https://bugs.kde.org/show_bug.cgi?id=385411
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=385410
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=385409
Florian Weimer changed:
What|Removed |Added
Attachment #114302|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #29 from Florian Weimer ---
Created attachment 114302
--> https://bugs.kde.org/attachment.cgi?id=114302&action=edit
Use guarded loads in the guest
This patch changes the guest code to use guarded loads.
However, this insuf
https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #28 from Florian Weimer ---
Found it:
/* A ternary if-then-else operator. It returns iftrue if cond is
nonzero, iffalse otherwise. Note that it is STRICT, ie. both
iftrue and iffalse are
https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #27 from Florian Weimer ---
Hopefully someone can see what is wrong with the generated IR:
vll %v0,%r4,0(%r2)
-- IMark(0x401892E, 6, 0) --
t6 = Add64(0x0:I64,GET:I64(592))
t7 = GET:I32
https://bugs.kde.org/show_bug.cgi?id=385409
--- Comment #26 from Florian Weimer ---
The SIGSEGV happens here in the generated code:
(gdb) disas 0x0010038c9230,+20
Dump of assembler code from 0x10038c9230 to 0x10038c9244:
0x0010038c9230
https://bugs.kde.org/show_bug.cgi?id=385409
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--- Comment #25 from
https://bugs.kde.org/show_bug.cgi?id=390871
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=395682
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=388862
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381805
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381769
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381556
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381509
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381514
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381289
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=377700
--- Comment #1 from Florian Weimer ---
To work around this issue, you should link the rdkafka application dynamically.
Even if we fix the bug you reported, valgrind will not be able to recognize
memory allocations in a statically linked application
https://bugs.kde.org/show_bug.cgi?id=377700
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
50 matches
Mail list logo
