[valgrind] [Bug 488379] --track-fds=yes generates errors that cannot be suppressed for valgrind internal --xml-file=

https://bugs.kde.org/show_bug.cgi?id=488379 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[PATCH] doc: Always distribute all man pages

dist targets shouldn't depend on configure conditionals. * doc/Makefile.am: Remove DEBUGINFOD and LIBDEBUGINFOD from dist targets. Add comments about which man pages go into which section. Signed-off-by: Mark Wielaard --- doc/Makefile.am | 33 +++-- 1

Re: make dist considered harmful: odd gotcha with building elfutils rpms

Hi Frank, On Tue, 2024-06-11 at 10:30 -0400, Frank Ch. Eigler wrote: > While trying to get a reliable fedora-copr build of the git/master > snapshot of elfutils, I ran into a problem that took me too long to > figure out. I was running "make rpm" from an elfutils build tree, > which involves

Re: elfutils DWARF problem was: Re: Problem with BTF generation on mips64el

Hi, Adding elfutils-devel to CC to keep everyone up to date on the state of the patches. On Mon, 2024-06-10 at 23:36 -0700, Tony Ambardar wrote: > On Mon, Jun 03, 2024 at 08:47:24PM -0700, Tony Ambardar wrote: > > On Mon, Jun 03, 2024 at 09:18:33PM +0200, Mark Wielaard wrote: > >

[valgrind] [Bug 487862] memcheck does not believe that bytes on new pages are Defined by brk() system call

https://bugs.kde.org/show_bug.cgi?id=487862 --- Comment #9 from Mark Wielaard --- Hi John, (In reply to John Reiser from comment #8) > What has changed is very large apps such as qemu-user-* which depend on > dozens of "random" libraries, and the system > builders/maintai

[valgrind] [Bug 487862] memcheck does not believe that bytes on new pages are Defined by brk() system call

https://bugs.kde.org/show_bug.cgi?id=487862 --- Comment #6 from Mark Wielaard --- BTW it seems this whole discussion is duplicated in the comments of memcheck/mc_main.c mc_post_clo_init () // We assume that brk()/sbrk() does not initialise new memory. ... With as conclusion: // So we

[valgrind] [Bug 487862] memcheck does not believe that bytes on new pages are Defined by brk() system call

https://bugs.kde.org/show_bug.cgi?id=487862 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #4 from Mark

Re: F35 Change: Debuginfod By Default (Self-Contained Change proposal)

Hi Panu, On Wed, Jun 05, 2024 at 09:26:14AM +0300, Panu Matilainen wrote: > On 6/4/24 21:43, Frank Ch. Eigler wrote: > >dvlasenk wrote: > > > >>[...] Do you understand how many fetches of debuginfo will be > >>attempted by e.g. a kernel build tooling when it runs readelf on 8000 > >>freshly

[PATCH 2/2] readelf: add pretty printing for FDO Dlopen Metadata note

From: Luca Boccassi The node ID and the string format are now fixed, even if the content of the string might change, it will still be a string. * libebl/eblobjnote.c (ebl_object_note): Handle both type being NT_FDO_PACKAGING_METADATA or NT_FDO_DLOPEN_METADATA when name is "FDO".

[PATCH 1/2] libelf: Sync elf.h from glibc

* libelf/elf.h: Adds AT_HWCAP{3,4}, NT_FDO_DLOPEN_METADATA and R_LARCH_TLS_DESC{32,64}. Signed-off-by: Mark Wielaard --- libelf/elf.h | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/libelf/elf.h b/libelf/elf.h index f2206e5c065d..081742a9c38c

Re: [PATCH] readelf: add pretty printing for FDO Dlopen Metadata note

Hi Luca, On Thu, 2024-05-30 at 11:45 +0100, Luca Boccassi wrote: > On Tue, 14 May 2024 at 22:18, Mark Wielaard wrote: > > Not a fan of json, feels very un-ELF. But it is what it is. The patch > > looks OK. Could you let us know when the elf.h change is accepted in > > g

Re: Sourceware @ Conservancy - Year One

Hi Maxim, On Thu, May 30, 2024 at 12:18:38PM +0400, Maxim Kuvyrkov via Overseers wrote: > > On May 29, 2024, at 23:02, Mark Wielaard wrote: > > And a special thanks to ARM who have been using > > https://patchwork.sourceware.org/ to provide a pre-commit testing > > serv

Re: [committed v2 0/2] VAX: Fix issues with FP format option documentation

Hi Maciej (Hi David, added to CC), On Mon, 2024-05-27 at 05:19 +0100, Maciej W. Rozycki wrote: > As reported in PR target/79646 and fixed by a change proposed by Abe we > have a couple of issues with the descriptions of the VAX floating-point > format options in the option definition file.

[valgrind] [Bug 487439] SIGILL in JDK11, JDK17

https://bugs.kde.org/show_bug.cgi?id=487439 --- Comment #10 from Mark Wielaard --- (In reply to Paul Floyd from comment #9) > diff --git a/VEX/priv/guest_amd64_toIR.c b/VEX/priv/guest_amd64_toIR.c > index f0b1c5516..28c37f092 100644 > --- a/VEX/priv/guest_amd64_toIR.c > ++

Re: FSF copyright assignment

Hi Seyed, On Sat, May 25, 2024 at 11:34:53AM +0100, Seyed Sajad Kahani via Gcc wrote: > I am writing to request the FSF copyright assignment forms, as they > are a legal requirement for contributing to GCC. At https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright you'll find the

[valgrind] [Bug 487439] SIGILL in JDK11, JDK17

https://bugs.kde.org/show_bug.cgi?id=487439 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #8 from Mark

Re: Wrong date

Hi Tony, On Wed, May 22, 2024 at 06:58:34PM -0500, tony.antonucci--- via Gcc wrote: > This was for the gcc 14.1 release. > Sorry I omitted that in the first email. Thanks for the notice, this has been fixed now:

[valgrind] [Bug 487296] --track-fds=yes and --track-fds=all report erroneous information when fds 0, 1, or 2 are used as non-std

https://bugs.kde.org/show_bug.cgi?id=487296 --- Comment #3 from Mark Wielaard --- For each inherited fd VG_(init_preopened_fds) calls ML_(record_fd_open_named)(-1, fd); So the ThreadId will be -1. Which ML_(record_fd_open_with_given_name) documents as "If the tid is -1, this indi

[valgrind] [Bug 487296] --track-fds=yes and --track-fds=all report erroneous information when fds 0, 1, or 2 are used as non-std

https://bugs.kde.org/show_bug.cgi?id=487296 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 487296] --track-fds=yes and --track-fds=all report erroneous information when fds 0, 1, or 2 are used as non-std

https://bugs.kde.org/show_bug.cgi?id=487296 --- Comment #1 from Mark Wielaard --- Nice. Thanks for catching this. Yeah, it makes sense to start "tracking" std fds once they are closed (and reopened). One thought I had was that maybe this shouldn't be special cased for just stdin/out/

[valgrind] [Bug 487296] --track-fds=yes and --track-fds=all report erroneous information when fds 0, 1, or 2 are used as non-std

https://bugs.kde.org/show_bug.cgi?id=487296 Mark Wielaard changed: What|Removed |Added CC||ahajk...@redhat.com

Re: [COMMITTED] Regenerate riscv.opt.urls and i386.opt.urls

Hi, On Mon, 2024-05-20 at 12:37 -0400, David Malcolm wrote: > On Mon, 2024-05-20 at 16:19 +, Jiang, Haochen wrote: > > Thanks for your help! I haven't noticed this file is newly added to > > GCC. > > I suppose that is why the buildbot is reporting something the whole > > afternoon for me. > >

[COMMITTED] Regenerate riscv.opt.urls and i386.opt.urls

risc-v added an -mfence-tso option. i386 removed Xeon Phi ISA support options. But the opt.urls files weren't regenerated. Fixes: a6114c2a6911 ("RISC-V: Implement -m{,no}fence-tso") Fixes: e1a7e2c54d52 ("i386: Remove Xeon Phi ISA support") gcc/ChangeLog: * config/riscv/riscv.opt.urls:

[gcc r15-692] Regenerate riscv.opt.urls and i386.opt.urls

https://gcc.gnu.org/g:591bc70139d898c06b1d605ff4fed591ffd2e2e7 commit r15-692-g591bc70139d898c06b1d605ff4fed591ffd2e2e7 Author: Mark Wielaard Date: Mon May 20 13:13:02 2024 +0200 Regenerate riscv.opt.urls and i386.opt.urls risc-v added an -mfence-tso option. i386 removed Xeon Phi

[Dwarf-discuss] strx use in debug_line table

Hi, Section 6.2.4.1 Standard Content Descriptions under 1. DW_LNCT_path has the following description on using DW_FORM_strx forms: In a .debug_line.dwo section, the forms DW_FORM_strx, DW_FORM_strx1, DW_FORM_strx2, DW_FORM_strx3 and DW_FORM_strx4 may also be used. These refer into the

Re: [PATCH] readelf: add pretty printing for FDO Dlopen Metadata note

Hi Luca, On Fri, May 10, 2024 at 10:58:02PM +0100, luca.bocca...@gmail.com wrote: > Note that the webpage in the comment is not published yet, > it will be next week when the next systemd RC is tagged. > The document can be viewed right now on github at: >

Re: [PATCH] Fix 'make coverage' when used with lcov version 2.0+

Hi, I think things worked out in the end, so that is good. Personally I didn't think Dmitry's request to take his review into account was exaggerating. But that might be because I know him and am happy with his suggestions in general. If the tone of some request was interpreted as "not

Re: [rfc] [patch] PR28204: debuginfod ima signature verification

Hi Aaron, On Thu, 2024-05-09 at 13:56 -0400, Aaron Merey wrote: > I know there's already been a lot of discussion re. ima:permissive and > I'm weighing in rather late, but FWIW I do support including it. > Currently individual ELF sections cannot be downloaded when > ima:enforcing is active.

Re: [PATCH] readelf: Fix printing of DW_FORM_strx and DW_MACRO parsing

Hi, On Sun, 2024-05-05 at 00:15 +0200, Mark Wielaard wrote: > print_form_data didn't take the offset_len (4 or 8 bytes) into account > causing the wrong entry to be read from .debug_str_offsets. > print_debug_macro_section did sanity checking before calling > print_form_data, which

Re: [EXTERNAL] [COMMITTED] Regenerate cygming.opt.urls and mingw.opt.urls

Hi Evgeny, Adding David to the CC, who might know the details. On Mon, May 13, 2024 at 08:44:12AM +, Evgeny Karpov wrote: > Sunday, May 12, 2024 > > Thank you for reviewing our changes related to the refactoring of > extracting the MinGW implementation from ix64. > > It was expected to move

Re: [PATCH] ar: Replace one alloca use by xmalloc

Hi Aaron, On Fri, May 10, 2024 at 05:16:06PM -0400, Aaron Merey wrote: > On Tue, Apr 30, 2024 at 10:39 AM Mark Wielaard wrote: > > > > This alloca use is inside a lexical block and is used to replace one > > element of argv. Use a function local variable, xmalloc and fr

[COMMITTED] Regenerate cygming.opt.urls and mingw.opt.urls

The new cygming.opt.urls and mingw.opt.urls in the gcc/config/mingw/cygming.opt.urls directory need to generated by make regenerate-opt-urls in the gcc subdirectory. They still contained references to the gcc/config/i386 directory from which they were copied. Fixes: 1f05dfc131c7 ("Reuse MinGW

[gcc r15-387] Regenerate cygming.opt.urls and mingw.opt.urls

https://gcc.gnu.org/g:a18c83b45c64ac7870f6e2acb0f23ae6090ed9cd commit r15-387-ga18c83b45c64ac7870f6e2acb0f23ae6090ed9cd Author: Mark Wielaard Date: Sun May 12 14:37:58 2024 +0200 Regenerate cygming.opt.urls and mingw.opt.urls The new cygming.opt.urls and mingw.opt.urls

Sourceware Open Office, Friday 16:00 UTC

Friday May 10, 16:00 UTC, irc.libera.chat #overseers (Today in about 1 hour) To get the right time in your local timezone: $ date -d "Fri May 10 16:00:00 UTC 2024" Lots of discussion topics: - Sourceware 2024 - The Plan https://inbox.sourceware.org/20240325095827.gi5...@gnu.wildebeest.org/ -

[valgrind] [Bug 317127] Fedora18/x86_64 --sanity-level=3 : aspacem segment mismatch

https://bugs.kde.org/show_bug.cgi?id=317127 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #18 from Mark

[PATCH] readelf: Fix printing of DW_FORM_strx and DW_MACRO parsing

calling print_form_data. * tests/testfileclangmacro.bz2: New testfile. * tests/Makefile.am (EXTRA_DIST): Add testfileclangmacro.bz2. * tests/run-readelf-macro.sh: Add testfileclangmacro output. Signed-off-by: Mark Wielaard --- src/readelf.c| 13 +- tests

Re: Updated Sourceware infrastructure plans

Hi Jeff, On Wed, 2024-05-01 at 15:38 -0600, Jeff Law wrote: > What works well? If you've wired up some CI bits, it's is extremely > useful to test an under development patch. Develop, push a branch, > raise an MR. At that point the CI system kicks in. Subsequent pushes > to the branch

Re: Updated Sourceware infrastructure plans

Hi Jason, On Wed, May 01, 2024 at 04:04:37PM -0400, Jason Merrill wrote: > On 5/1/24 12:15, Jeff Law wrote: > >We're currently using patchwork to track patches tagged with > >RISC-V.  We don't do much review with patchwork.  In that model > >patchwork ultimately just adds overhead as I'm

Re: Updated Sourceware infrastructure plans

Hi Jonathan, On Wed, May 01, 2024 at 08:38:26PM +0100, Jonathan Wakely wrote: > On Wed, 1 May 2024 at 20:19, Jeff Law via Gcc wrote: > > We're currently using patchwork to track patches tagged with RISC-V. We > > don't do much review with patchwork. In that model patchwork ultimately > > just

[PATCH] ar: Replace one alloca use by xmalloc

. Signed-off-by: Mark Wielaard --- src/ar.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/ar.c b/src/ar.c index e6d6d58f2b3b..fcb8bfb90a9f 100644 --- a/src/ar.c +++ b/src/ar.c @@ -41,6 +41,7 @@ #include #include +#include "libeu.h" #include "arlib.h&

[valgrind] [Bug 486180] [Valgrind][MIPS] 'VexGuestArchState' has no member named 'guest_IP_AT_SYSCALL'

https://bugs.kde.org/show_bug.cgi?id=486180 Mark Wielaard changed: What|Removed |Added CC||ar...@linux.ibm.com --- Comment #7 from Mark

[valgrind] [Bug 486293] New: memccpy false positives

https://bugs.kde.org/show_bug.cgi?id=486293 Bug ID: 486293 Summary: memccpy false positives Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED

[valgrind] [Bug 486180] [Valgrind][MIPS] 'VexGuestArchState' has no member named 'guest_IP_AT_SYSCALL'

https://bugs.kde.org/show_bug.cgi?id=486180 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED

[Valgrind-users] Valgrind-3.23.0 is available

We are pleased to announce a new release of Valgrind, version 3.23.0, available from https://valgrind.org/downloads/current.html. See the release notes below for details of changes. Our thanks to all those who contribute to Valgrind's development. This release represents a great deal of time,

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added CC||v...@altlinux.org --- Comment #6 from Mark

[valgrind] [Bug 482358] Feature Request: Add --track-fds=error

https://bugs.kde.org/show_bug.cgi?id=482358 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED

[Valgrind-users] Valgrind-3.23.0.RC2 is available for testing

Andreas Arnez (1): s390x: Improve operand names in trackers for PRNO Mark Wielaard (11): 32 bit new_delete_mismatch_size and sized_aligned_new_delete_misaligned .exp Add new .exp-32 files to memcheck/tests/Makefile.am EXTRA_DIST filter out in /absolute/path in drd/tests stderr filter Filter

[valgrind] [Bug 485924] No support for pidfd_send_signal system call

https://bugs.kde.org/show_bug.cgi?id=485924 --- Comment #3 from Mark Wielaard --- So the only tricky part is that we want to mimic this part of the (generic) PRE(sys_kill): /* If we're sending SIGKILL, check to see if the target is one of our threads and handle it specially

[valgrind] [Bug 485924] No support for pidfd_send_signal system call

https://bugs.kde.org/show_bug.cgi?id=485924 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

Re: [Valgrind-users] Valgrind-3.23.0.RC1 is available for testing

t of the stacktrace is slightly different on different systems. I tried to work around that with the following commit: commit 04d30049bf9b4ae14262a50e8a16442e1edf75f8 Author: Mark Wielaard Date: Tue Apr 23 14:14:33 2024 +0200 Filter away "main" differences in filter_fdleak St

Re: Updated Sourceware infrastructure plans

Hi, On Mon, Apr 22, 2024 at 11:51:00PM -0400, Jason Merrill wrote: > On Mon, Apr 22, 2024 at 11:24 PM Tom Tromey wrote: > > Jason> Someone mentioned earlier that gerrit was previously tried > > Jason> unsuccessfully. > > > > We tried it and gdb and then abandoned it. We tried to integrate it >

Re: Updated Sourceware infrastructure plans

Hi Joseph, On Thu, 2024-04-18 at 15:56 +, Joseph Myers wrote: > On Thu, 18 Apr 2024, Mark Wielaard wrote: > > > But we like to get more feedback on what people really think a > > "pull-request" style framework should look like. We used to have a > > gerrit

Re: Sourceware mitigating and preventing the next xz-backdoor

Hi Alejandro, On Wed, Apr 10, 2024 at 06:30:42PM +0200, Alejandro Colomar wrote: > It would also be interesting to require showing range-diffs between > patch revisions. They make it much more difficult to introduce a > vulnerability after a reviewer has turned its mins into approving the >

Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.23.0.RC1 is available for testing

Test results look fairly good on the platforms I tested. I did fix a couple of small (testcase) issues for x86: 32 bit new_delete_mismatch_size and sized_aligned_new_delete_misaligned .exp and s390x: filter out in /absolute/path in drd/tests stderr filter With those: RHEL 8.9/x86-64: ==

[Valgrind-users] Valgrind-3.23.0.RC1 is available for testing

An RC1 tarball for 3.23.0 is now available at https://sourceware.org/pub/valgrind/valgrind-3.23.0.RC1.tar.bz2 (md5sum = 6d36fd8981d6aab7350f12cc61973be5) (sha1sum = 6ff57d5981d774e446853e8b166be8a3bb324601) https://sourceware.org/pub/valgrind/valgrind-3.23.0.RC1.tar.bz2.asc Please give it a try

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Attachment #168679|0 |1 is obsolete

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 --- Comment #2 from Mark Wielaard --- Created attachment 168679 --> https://bugs.kde.org/attachment.cgi?id=168679=edit core errors gensuppressions support Initial implementation for --gen-suppressions support for core errors With this the testc

[valgrind] [Bug 485778] Crash with --track-fds=all and --gen-suppressions=all

https://bugs.kde.org/show_bug.cgi?id=485778 Mark Wielaard changed: What|Removed |Added Assignee|jsew...@acm.org |m...@klomp.org Status|REPORTED

[valgrind] [Bug 328563] make track-fds support xml output

https://bugs.kde.org/show_bug.cgi?id=328563 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found

https://bugs.kde.org/show_bug.cgi?id=362680 --- Comment #4 from Mark Wielaard --- bug #328563 has an attachment that implements this -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #8 from Mark Wielaard --- (In reply to Andreas Arnez from comment #7) > (In reply to Andreas Arnez from comment #6) > > Created attachment 168623 [details] > > Updated version of the extension proposal > I pushed this now

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #5 from Mark Wielaard --- I haven't reviewed the fully proposal, but in general I like the idea of using the same mechanism as the syscalls for instrumenting these more complex instructions. It is at least familiar. You might want to rename

[valgrind] [Bug 450705] s390x: Add NNPA support (arch14)

https://bugs.kde.org/show_bug.cgi?id=450705 --- Comment #3 from Mark Wielaard --- Extension idea was posted to the mailinglist: https://sourceforge.net/p/valgrind/mailman/message/58753610/ -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64

https://bugs.kde.org/show_bug.cgi?id=485276 --- Comment #4 from Mark Wielaard --- (In reply to Mark Wielaard from comment #3) > I am unable to replicate this with either clang version 17.0.6 or 18.1.2, > not with -O2 or -O1. On x86_64. Missed that the original report was against arm64

[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64

https://bugs.kde.org/show_bug.cgi?id=485276 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #3 from Mark

[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (g++)

https://bugs.kde.org/show_bug.cgi?id=472329 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 CC

[valgrind] [Bug 481874] Add arm64 support for FreeBSD

https://bugs.kde.org/show_bug.cgi?id=481874 --- Comment #17 from Mark Wielaard --- .git-blame-ignore-revs references a clang-format rev that doesn't exist in tree. Makefile.all.am and Makefile.tool.am look correct. NEWS OK. VEX changes OK, except for unnecessarily extending VexGuestARM64State

[COMMITTED] gcc-mingw don't enable rust

gccrs now requires cargo to build --- builder/master.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builder/master.cfg b/builder/master.cfg index c75b1622331f..97bf3703c019 100644 --- a/builder/master.cfg +++ b/builder/master.cfg @@ -3511,7 +3511,7 @@

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #7 from Mark Wielaard --- There is now also an fedora eln build: https://koji.fedoraproject.org/koji/buildinfo?buildID=2437715 Since eln is build with -march=x86-64-v3 this might be a good testing environment. Please let me know if you

[COMMITTED] Regenerate c.opt.urls

Fixes: df7bfdb7dbf2 ("c++: reference cast, conversion fn [PR113141]") A new warning option -Wcast-user-defined was added to c.opt and documented in doc/invoke.texi. But c.opt.urls wasn't regenerate. gcc/c-family/ChangeLog: * c.opt.urls: Regenerate. --- gcc/c-family/c.opt.urls | 3 +++

[gcc r14-9957] Regenerate c.opt.urls

https://gcc.gnu.org/g:a9d3b3caef87d76072c946145d21e7606b303e12 commit r14-9957-ga9d3b3caef87d76072c946145d21e7606b303e12 Author: Mark Wielaard Date: Sat Apr 13 23:02:14 2024 +0200 Regenerate c.opt.urls Fixes: df7bfdb7dbf2 ("c++: reference cast, conversion fn [PR1

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 --- Comment #6 from Mark Wielaard --- (In reply to Mark Wielaard from comment #5) > I'll add it to the next fedora rawhide valgrind build so we can test it a > bit more. There is now valgrind-3.22.0-8.fc41 with this and some other (x86-64-v3)

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[valgrind] [Bug 485487] glibc built with -march=x86-64-v3 does not work due to ld.so strcmp

https://bugs.kde.org/show_bug.cgi?id=485487 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark

[valgrind] [Bug 463458] memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 target

https://bugs.kde.org/show_bug.cgi?id=463458 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system

https://bugs.kde.org/show_bug.cgi?id=463463 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32

https://bugs.kde.org/show_bug.cgi?id=481127 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32

https://bugs.kde.org/show_bug.cgi?id=481127 --- Comment #10 from Mark Wielaard --- Created attachment 168440 --> https://bugs.kde.org/attachment.cgi?id=168440=edit valgrind.fma_arm64.diff This is the variant of the patch that I tested. It looks good to me. How should we credit this w

[valgrind] [Bug 481127] [PATCH] amd64: Implement VFMADD213 for Iop_MAddF32

https://bugs.kde.org/show_bug.cgi?id=481127 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0

[valgrind] [Bug 463458] memcheck/tests/vcpu_fnfns fails when glibc is built for x86-64-v3 target

https://bugs.kde.org/show_bug.cgi?id=463458 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark

[valgrind] [Bug 463456] memcheck/tests/origin6-fp fails when building for x86-64-v3 target

https://bugs.kde.org/show_bug.cgi?id=463456 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark

[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system

https://bugs.kde.org/show_bug.cgi?id=463463 --- Comment #2 from Mark Wielaard --- These seem rounding issues, fixed by https://bugs.kde.org/show_bug.cgi?id=481127 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 463463] none/tests/amd64/fma fails when executed under valgrind on a x86-64-v3 system

https://bugs.kde.org/show_bug.cgi?id=463463 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark

Re: [rfc] [patch] PR28204: debuginfod ima signature verification

Hi Frank, On Wed, Apr 10, 2024 at 05:01:36PM -0400, Frank Ch. Eigler wrote: > > > - to drop "permissive" mode > > > > We discussed a bit on irc about "wording". But I think it isn't really > > how it is worded, but that there is just different features. What is > > called "enforcing" is an

Re: [PATCH] libdw: dwarf_getsrcfiles should not imply dwarf_getsrclines

Hi Aaron, On Wed, Apr 10, 2024 at 04:43:53PM -0400, Aaron Merey wrote: > > > - /* Pass the file data structure to the caller. */ > > > - if (filesp != NULL) > > > -*filesp = files; > > > + const char **newdirs = (void *) >info[nnewfiles]; > > > + const char **prevdirs = (void *)

Re: [PATCH] libdw: dwarf_getsrcfiles should not imply dwarf_getsrclines

Hi Aaron, On Tue, 2024-04-09 at 23:45 -0400, Aaron Merey wrote: > dwarf_getsrcfiles causes line data to be read in addition to file data. > This is wasteful for programs which only need file or directory names. > Debuginfod server is one such example. > > Fix this by moving the srcfile reading

[valgrind] [Bug 377966] arm64 unhandled instruction dc zva

https://bugs.kde.org/show_bug.cgi?id=377966 Mark Wielaard changed: What|Removed |Added Summary|Error message said to |arm64 unhandled instruction

[valgrind] [Bug 479600] Segmentation fault launching the valgrind (mipsel-openwrt-linux-musl-gcc)

https://bugs.kde.org/show_bug.cgi?id=479600 Mark Wielaard changed: What|Removed |Added Summary|Segmentation fault |Segmentation fault

[valgrind] [Bug 481874] Add arm64 support for FreeBSD

https://bugs.kde.org/show_bug.cgi?id=481874 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #9 from Mark

Re: [rfc] [patch] PR28204: debuginfod ima signature verification

Hi Frank, On Wed, 2024-04-03 at 17:04 -0400, Frank Ch. Eigler wrote: > The following raw diff reworks this long-blocked patch to overcome > these three objections last fall: > > - to drop "permissive" mode We discussed a bit on irc about "wording". But I think it isn't really how it is worded,

Re: Patches submission policy change

Hi Jonathan, On Sun, Apr 07, 2024 at 03:20:42PM +0100, Jonathan Wakely wrote: > On Sun, 7 Apr 2024, 15:02 Mark Wielaard, wrote: > > The jit mailinglist is the same. It only has one moderator > > (David). Having a second/backup one would probably be nice. Are you ok

Re: Elfutils Code of Conduct

dual is officially representing the community > in public spaces. Examples of representing our community include acting > as an appointed representative at an online or offline event. > > ## Enforcement > > Instances of abusive, harassing, or otherwise unacceptable behavior may &g

Re: Patches submission policy change

Hi Jonathan, On Sun, Apr 07, 2024 at 01:32:11PM +0100, Jonathan Wakely via Gdb wrote: > On Thu, 4 Apr 2024, 22:36 Mark Wielaard, wrote: > > wrt to the mailinglists maybe getting larger patches, I think most > > will still be under 400K and I wouldn't raise the limit (because most

Re: Patches submission policy change

Hi, On Fri, 2024-04-05 at 09:17 +0200, Christophe Lyon wrote: > On 4/4/24 23:35, Mark Wielaard wrote: > > wrt to the mailinglists maybe getting larger patches, I think most > > will still be under 400K and I wouldn't raise the limit (because most > > such larger emails

Re: [PATCH] strip: Add check for elf_begin() result

Hi Maks, On Fri, Apr 05, 2024 at 09:53:03PM +0300, Maks Mishin wrote: > Return value of a function 'elf_begin' is dereferenced at strip.c:1166 > without checking for NULL, but it is usually checked for this function. Please stop sending these "patches" till you actually understand the code. In

[COMMITTED] Regenerate common.opt.urls

The new support for gcov modified condition/decision coverage introduced two new flags for gcc, -Wcoverage-too-many-conditions and -fcondition-coverage. But didn't regenerate the gcc/common.opt.urls. Fixes: 08a52331803f ("Add condition coverage (MC/DC)") gcc/ChangeLog: *

[gcc r14-9812] Regenerate common.opt.urls

https://gcc.gnu.org/g:0c22f67526d72aa451633d5212259a8f75e59a44 commit r14-9812-g0c22f67526d72aa451633d5212259a8f75e59a44 Author: Mark Wielaard Date: Fri Apr 5 17:22:16 2024 +0200 Regenerate common.opt.urls The new support for gcov modified condition/decision coverage

  1   2   3   4   5   6   7   8   9   10   >