Hi Carl,
On Fri, Jan 17, 2025 at 11:30:30AM -0800, Carl Love wrote:
> fatal: unable to access 'https://gcc.gnu.org/git/gcc.git/': The
> requested URL returned error: 500
> program finished with exit code 128
> elapsedTime=0.724754
>
> It looks like it wasn't able to complete the git clone or pull
Hi Monk,
On Fri, Nov 15, 2024 at 06:53:09PM +0800, Monk Chiang wrote:
> gcc/ChangeLog:
> * gcc/config/riscv/riscv.cc
> (riscv_file_end_indicate_exec_stack): Add .note.gnu.property.
> * gcc/config/riscv/linux.h (TARGET_ASM_FILE_END): Define.
>
> [...]
> diff --git a/gcc/config/ri
Hi Ihor,
On Thu, Jan 16, 2025 at 08:44:54PM +, Ihor Solodrai via Gcc wrote:
> An example of successful test run (you have to login to github to see
> the logs):
> https://github.com/kernel-patches/bpf/actions/runs/12816136141/job/35736973856
>
> Currently 2513 of 4340 tests pass for GCC BPF,
Hi Nick,
On Fri, Jan 17, 2025 at 10:31:49AM +, Nick Clifton wrote:
> >But I also think this is a bug in binutils readelf (CCing nickc).
> >
> >It really should not even try to print the "interpreter" of a separate
> >debuginfo file.
>
> Well yes and no. One of the main uses of readelf is to
Hi! (Added nickc to the CC, see below)
On Wed, Jan 15, 2025 at 01:52:24PM +0100, Miro Hrončok wrote:
> On 15. 01. 25 10:18, Robin Jarry wrote:
> >I found out that rpmlint errors out without producing any meaningful result
> >when the analyzed RPMs contain binaries:
> >
> > sh-5.2# strace -f -e tr
Native configuration is riscv64-unknown-linux-gnu
=== gcc tests ===
Running target unix
FAIL: c-c++-common/spec-barrier-1.c -Wc++-compat (test for excess errors)
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
https://bugs.kde.org/show_bug.cgi?id=498143
--- Comment #2 from Mark Wielaard ---
Also pushed to VALGRIND_3_24_BRANCH
commit b732f86998e39ca8714330f487804428b54c481c
Author: Mark Wielaard
Date: Wed Jan 8 16:52:03 2025 +0100
linux: support EVIOCGRAB ioctl
EVIOCGRAB just takes an
https://bugs.kde.org/show_bug.cgi?id=498317
--- Comment #3 from Mark Wielaard ---
Also added to the VALGRIND_3_24_BRANCH
commit febe1ccef09f70777b086f938c03f3e71989a7c8
Author: Paul Floyd
Date: Tue Jan 7 08:05:20 2025 +0100
Bug 498317 - FdBadUse is not a valid CoreError type in a
Friday Jan 10, 16:00 UTC
https://bbb.sfconservancy.org/b/mar-aom-dmo-fko
Using #overseers on irc.libera.chat as backup.
To get the right time in your local timezone:
$ date -d "Fri Jan 10 16:00 UTC 2025"
Lets celebrate what went well in 2024 and what we will do even better
in 2025! Email? Patchwo
https://bugs.kde.org/show_bug.cgi?id=498143
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
Hi Jakub,
On Tue, 2025-01-07 at 20:22 +0100, Jakub Jelinek wrote:
> DWARF has voted in yesterday https://dwarfstd.org/issues/241209.1.html ,
> which is basically just a guarantee that the DWARF 6 draft
> DW_AT_language_{name,version} attribute codes and content of
> https://dwarfstd.org/languages-
file and directory arguments.
Signed-off-by: Mark Wielaard
---
config/Makefile.am | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/config/Makefile.am b/config/Makefile.am
index 2dcbe94eaef1..11693ed47dad 100644
--- a/config/Makefile.am
+++ b/config/Makefile.am
@@ -42,9
https://bugs.kde.org/show_bug.cgi?id=498317
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
https://gcc.gnu.org/g:668cad04b16fc044142474232ac072fcc5f94433
commit r15-6598-g668cad04b16fc044142474232ac072fcc5f94433
Author: Mark Wielaard
Date: Sun Jan 5 18:00:36 2025 +0100
tree-switch-conversion: don't apply switch size limit on jump tables
commit 56946c801a7c (&q
commit 56946c801a7c ("gimple: Add limit after which slower switchlower
algs are used [PR117091] [PR117352]") introduced a limit on the number
of cases of a switch. It also bails out on finding jump tables if the
switch is too large. This introduces a compile time regression during
bootstrap. A risc
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=498103
Bug ID: 498103
Summary: Clean up/merge linux sys_ptrace PRE/POST wrappers
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Linux
Hi,
On Mon, 2024-12-30 at 01:25 +0100, Mark Wielaard wrote:
> If desthdr is ".got.plt" search for the actual ".got" section and make
> sure the _GLOBAL_OFFSET_TABLE_ points to it.
>
> * backends/riscv_symbol.c (riscv_check_special_symbol): Check
> s
If desthdr is ".got.plt" search for the actual ".got" section and make
sure the _GLOBAL_OFFSET_TABLE_ points to it.
* backends/riscv_symbol.c (riscv_check_special_symbol): Check
sname is ".got.plt", find ".got" scn to check sym st_value.
Sig
Hi,
On Sun, Dec 29, 2024 at 07:38:03PM +, buil...@sourceware.org wrote:
> A new failure has been detected on builder elfutils-ubuntu-riscv while
> building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/274/builds/133
>
> Build state: f
https://bugs.kde.org/show_bug.cgi?id=497977
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #83 from Mark Wielaard ---
Created attachment 176918
--> https://bugs.kde.org/attachment.cgi?id=176918&action=edit
riscv64: Add hardwire for ld-linux-riscv64-lp64d.so.1 strcmp
When using dlopen ld.so can end up i
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #82 from Mark Wielaard ---
Created attachment 176883
--> https://bugs.kde.org/attachment.cgi?id=176883&action=edit
riscv64: syswrap various shared linux syscalls
syswrap-riscv64-linux.c: Hook up open_tree, move_mount, fsopen,
f
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #81 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #78)
> Found that there are there are other arches that restrict highest user space
> address, so I propose the following patch which makes sh-mem-random pass on
>
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #80 from Mark Wielaard ---
I keep hitting
compressed.o: in function `test_compressed_10':
/home/mark/valgrind/none/tests/riscv64/compressed.c:347:(.text+0x56d26):
dangerous relocation: The addend isn't allowed for R_RISCV_GOT_HI2
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176817|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #78 from Mark Wielaard ---
(In reply to JojoR from comment #10)
> (In reply to Petr Pavlu from comment #9)
> > (In reply to Paul Floyd from comment #8)
> > > Are the other failures "reaonable"?
> >
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #76 from Mark Wielaard ---
Created attachment 176828
--> https://bugs.kde.org/attachment.cgi?id=176828&action=edit
integer.c: replace zero by a1
Simplest seems to be to replace the usage of "zero" in the branch instruc
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #75 from Mark Wielaard ---
Trying to figure out:
integer.c: Assembler messages:
integer.c:132: Error: illegal operands `la zero,0'
integer.c:132 is:
TESTINST_0_2_Bxx_COND(4, "beq a0, zero, 1f", 0, 0, a0, zero);
TESTIN
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176588|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176664|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176583|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176584|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #74 from Mark Wielaard ---
Rebased patches also pushed here:
https://forge.sourceware.org/mjw/valgrind/src/branch/riscv64-linux
We really have to figure out why/how to build the integer and compressed
testcases.
The fence.tso patch is
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #73 from Mark Wielaard ---
Created attachment 176817
--> https://bugs.kde.org/attachment.cgi?id=176817&action=edit
VEX/priv/guest_riscv64_toIR.c: Recognize both fence and fence.tso
fence.tso is used for __atomic_threa
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #72 from Mark Wielaard ---
Created attachment 176816
--> https://bugs.kde.org/attachment.cgi?id=176816&action=edit
Disable none/tests/riscv64 compressed and integer builds and test
Till we can figure out what the correct configure
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176585|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176582|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176581|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #176580|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #63 from Mark Wielaard ---
(In reply to Paul Floyd from comment #62)
> I've pushed a fix that turns off the warning rather than turning off the
> exec stack.
Thanks. That resolves two more failures. Only a handful left.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #61 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #54)
> Created attachment 176664 [details]
> VEX/priv/ir_opt.c: Also fold Iop_And1 expressions when possible
>
> Another fix for the issue seen in comment #52
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #60 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #55)
> nestedfns fails with:
>
> +Process terminating with default action of signal 11 (SIGSEGV)
> + Bad permissions for mapped region at address 0x
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #59 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #39)
> Created attachment 176588 [details]
> close_range fd as Int
>
> The double_close_range failure seems to be because the close_range wrapper
> is usi
Sourceware infrastructure community updates for Q4 2024
Sourceware has provided the infrastructure for core toolchain and
developer tools projects for more than 25 years.
https://sourceware.org/sourceware-25-roadmap.html
The last couple of years it has transformed from a purely volunteer
into a p
Sourceware infrastructure community updates for Q4 2024
Sourceware has provided the infrastructure for core toolchain and
developer tools projects for more than 25 years.
https://sourceware.org/sourceware-25-roadmap.html
The last couple of years it has transformed from a purely volunteer
into a p
Sourceware infrastructure community updates for Q4 2024
Sourceware has provided the infrastructure for core toolchain and
developer tools projects for more than 25 years.
https://sourceware.org/sourceware-25-roadmap.html
The last couple of years it has transformed from a purely volunteer
into a p
Sourceware infrastructure community updates for Q4 2024
Sourceware has provided the infrastructure for core toolchain and
developer tools projects for more than 25 years.
https://sourceware.org/sourceware-25-roadmap.html
The last couple of years it has transformed from a purely volunteer
into a p
Sourceware infrastructure community updates for Q4 2024
Sourceware has provided the infrastructure for core toolchain and
developer tools projects for more than 25 years.
https://sourceware.org/sourceware-25-roadmap.html
The last couple of years it has transformed from a purely volunteer
into a p
On Mon, Dec 09, 2024 at 11:24:39AM +0100, Mark Wielaard wrote:
> On Mon, 2024-12-02 at 11:16 +0100, Mark Wielaard wrote:
> > Adjust the DCO text to match the broader community usage and
> > clarifications around the use of real names, known identities and
> > (anonymous) pseud
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #58 from Mark Wielaard ---
And on the p550 with gcc 13.3.0, binutils 2.42.0 and glibc 2.39:
== 744 tests, 4 stderr failures, 1 stdout failure, 0 stderrB failures, 1
stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #57 from Mark Wielaard ---
make regtest (all above patches applied and integer and compressed tests
disabled) on a visionfive 2
with gcc 13.2.0, binutils 2.41 and glibc 2.38
== 744 tests, 3 stderr failures, 2 stdout failures, 0 stderrB
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #56 from Mark Wielaard ---
The compressed and integer tests don't compile with gcc 13.2.0 and binutils
2.41 and produce the same error message:
gcc -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -o
compr
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #55 from Mark Wielaard ---
On a pioneer box with fedora 38, glibc-2.37-5.fc38.riscv64, GCC 14.2.0,
Binutils 2.43.1, GDB 15.1 and all above patches applied:
== 743 tests, 3 stderr failures, 4 stdout failures, 0 stderrB failures, 1
stdoutB
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #54 from Mark Wielaard ---
Created attachment 176664
--> https://bugs.kde.org/attachment.cgi?id=176664&action=edit
VEX/priv/ir_opt.c: Also fold Iop_And1 expressions when possible
Another fix for the issue seen in comment #52.
This
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #53 from Mark Wielaard ---
Fix for comment #52
diff --git a/VEX/priv/host_riscv64_isel.c b/VEX/priv/host_riscv64_isel.c
index 76fc3fd5c..6921a47db 100644
--- a/VEX/priv/host_riscv64_isel.c
+++ b/VEX/priv/host_riscv64_isel.c
@@ -1161,6
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #52 from Mark Wielaard ---
On a fedora system I saw an issue with testcases that invoked bash, and also
when running bash itself under valgrind.
It does an And1(0:I1,t6))
So an AND against False [0], which is odd in itself, since that
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #50 from Mark Wielaard ---
(In reply to Richard Jones from comment #45)
> Are you maintaining these patches in a git repo somewhere? It might be
> easier to follow that way.
I used the new/experimental sourceware forge to push
https://bugs.kde.org/show_bug.cgi?id=358980
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #12 from Mark
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #43 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #42)
> drd/tests/condvar fails with
>
> Other thread: waiting for notify
> Other thread: notified
> RISCV64 front end: standard
> disInstr(riscv64): unh
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #44 from Mark Wielaard ---
Both helgrind/tests/tls_threads and helgrind/tests/tls_threads2 fail because if
this warning:
+WARNING: could not find symbol for var stack_cache_actsize in libpthread.so.0
+=> pthread stack cache cannot
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #41 from Mark Wielaard ---
memcheck/tests/linux/bug480706 fails because mlock2 wasn't wrapped
diff --git a/coregrind/m_syswrap/syswrap-riscv64-linux.c
b/coregrind/m_syswrap/syswrap-riscv64-linux.c
index b959bc861..68c53b0bd 100644
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #42 from Mark Wielaard ---
drd/tests/condvar fails with
Other thread: waiting for notify
Other thread: notified
RISCV64 front end: standard
disInstr(riscv64): unhandled instruction 0x833F
disInstr(riscv64): 1000'0011 0011
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #40 from Mark Wielaard ---
The none/tests/mmap_o_direct failure comes from vki-riscv64-linux.h not
defining VKI_O_DIRECT.
With that defined the test passes.
diff --git a/include/vki/vki-riscv64-linux.h b/include/vki/vki-riscv64-linux.h
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #39 from Mark Wielaard ---
Created attachment 176588
--> https://bugs.kde.org/attachment.cgi?id=176588&action=edit
close_range fd as Int
The double_close_range failure seems to be because the close_range wrapper is
using unsigned
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #38 from Mark Wielaard ---
The none/tests/procfs-linux (stderr) issue was a change in the handling of
readlinkat.
Adding a POST handler fixes it and makes the test pass:
diff --git a/coregrind/m_syswrap/syswrap-riscv64-linux.c
b/coregrind
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #37 from Mark Wielaard ---
== 744 tests, 11 stderr failures, 1 stdout failure, 0 stderrB failures, 1
stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls(stdoutB)
memcheck/tests/linux/bug480706 (stderr
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #36 from Mark Wielaard ---
So disabling compressed and integer, but without a configure check because I
don't know precisely what to test for.
diff --git a/configure.ac b/configure.ac
index 7d3c1a99b..7828b0193 100755
--- a/configu
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #35 from Mark Wielaard ---
Also none/tests/riscv64/integer.c doesn't compile on my setup.
GCC 13.3.0
GNU Binutils 2.42.0.20240216
depbase=`echo integer.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #34 from Mark Wielaard ---
Got the same issue as Paul in comment #18
Maybe we can guard the none/tests/riscv64/compressed.c test with some configure
check?
It seems unfortunate to have such compile issues with shipping toolchains.
--
You
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #33 from Mark Wielaard ---
And in my rebase of patch 6 I forgot a \ at the end of one line:
diff --git a/helgrind/tests/tc11_XCHG.c b/helgrind/tests/tc11_XCHG.c
index 6ad44efac..e92b671b7 100644
--- a/helgrind/tests/tc11_XCHG.c
+++ b
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #32 from Mark Wielaard ---
One more change that should go into patch 1 riscv64: Add initial support: new
port-specific Valgrind files because since commit
6a28e665f8dd7c031aef5aa0eaa4acbbd8ba27a9 ("With --track-fds=yes warn when
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #158147|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #158152|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #158151|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #158150|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #158149|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Attachment #158148|0 |1
is obsolete
Friday Dec 13, 16:00 UTC
https://bbb.sfconservancy.org/b/mar-aom-dmo-fko
Using #overseers on irc.libera.chat as backup.
To get the right time in your local timezone:
$ date -d "Fri Dec 13 16:00 UTC 2024"
Sourceware relies on cooperation among a broad diversity of core
toolchain and developer tool
https://bugs.kde.org/show_bug.cgi?id=495483
--- Comment #5 from Mark Wielaard ---
I think normally distros come with a package that has a local install of the
validating documents.
e.g. on fedora you would install docbook-dtds so no outgoing network traffic is
needed:
Name: docbook
https://bugs.kde.org/show_bug.cgi?id=497130
Mark Wielaard changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=497236
Bug ID: 497236
Summary: memcheck support for golang binaries
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: R
https://bugs.kde.org/show_bug.cgi?id=497130
--- Comment #2 from Mark Wielaard ---
commit 7136316123c54aba37fdab166e1bf860e452a4ae
Author: Mark Wielaard
Date: Fri Dec 6 15:39:25 2024 +0100
Recognize new DWARF5 DW_LANG constants
When using --read-var-info=yes readdwarf3 will try to
Hi,
On Mon, 2024-12-02 at 11:16 +0100, Mark Wielaard wrote:
> Adjust the DCO text to match the broader community usage and
> clarifications around the use of real names, known identities and
> (anonymous) pseudonyms.
>
> These changes clarify what was meant by "real name
Hi Henning,
On Fri, Dec 06, 2024 at 01:01:34AM +0100, Henning Meyer wrote:
> it is the Cross-Origin-Resource-Sharing mechanism explained at
> https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
Thanks, this might be a good URL to include in a comment so others
know what the extra headers are t
Hi Kito,
On Thu, Dec 05, 2024 at 03:12:03PM +0800, Kito Cheng wrote:
> function_shape::get_name is the funciton for building intrinsic function name,
> the result should not be changed by others once it built.
>
> So add const to the return type to make sure no one change that by
> accident.
Thi
https://bugs.kde.org/show_bug.cgi?id=497130
Mark Wielaard changed:
What|Removed |Added
Assignee|jsew...@acm.org |m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=497130
Bug ID: 497130
Summary: Recognize new DWARF5 DW_LANG constants
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status:
Hi Frank, Hi Henning,
On Wed, 2024-12-04 at 19:40 -0500, Frank Ch. Eigler wrote:
> > This is my first attempt at implementing CORS support in debuginfod.
>
> Looks good to me really; will wait for a glance from others.
So the code looks correct if you want to handle the OPTION command and
add a
Hi,
On Fri, 2024-11-22 at 18:33 +0100, Mark Wielaard wrote:
> Pick up the language codes published after DWARF5 was published.
> The are listed at https://dwarfstd.org/languages.html
>
> Also adjust C language dectection in dwarf_getfuncs and update the
> dwarf_default_lower_bo
Hi Jeff,
On Sun, 2024-12-01 at 08:56 -0700, Jeff Law wrote:
> commit 148e20466c2c246df9472efed0f2ae94cb65a0f8
> Author: Matevos Mehrabyan
> Date: Mon Nov 11 13:00:10 2024 -0700
>
> [PATCH v6 09/12] Add symbolic execution support.
>
> Gives an opportunity to execute the code on bit
ting
>
> That did the job, thank you!
>
> On Sun, 1 Dec 2024, Mark Wielaard wrote:
> >
> > If that doesn't work we'll have to clean it up on the server.
>
> I believe things are fine?
>
> % git branch -la | cat
> * master
> remotes
Hi Bradley,
Thanks for following the discussion and your input.
We have also been discussing some policy wording changes on gcc-patches:
https://inbox.sourceware.org/gcc-patches/20241202101600.1041524-1-m...@klomp.org/T
If you have any suggestions for improving the actual wording change
that woul
Adjust the DCO text to match the broader community usage and
clarifications around the use of real names, known identities and
(anonymous) pseudonyms.
These changes clarify what was meant by "real name" and that it is not
required to be a "legal name" or any other stronger requirement than a
known
Hi Gerald,
On Sun, Dec 01, 2024 at 07:26:45PM +0100, Gerald Pfeifer wrote:
> On Fri, 23 Aug 2024, Eric Gallager wrote:
> >>> The branch, python-formatting has been created
> >>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit)
> >> Hmm, are you intentionally creating a branch for the
Hi Richard,
On Thu, Nov 28, 2024 at 06:52:28PM +, Richard W.M. Jones wrote:
> On Thu, Nov 28, 2024 at 06:30:14PM +0100, Mark Wielaard wrote:
> > As others already analyzed this is because debugedit added error
> > checking for gdb-add-index in debugedit 5.1. Which is good. Exce
Hi,
Sorry, I missed this thread. Please do feel free to file a bugzilla
against debugedit for these kind of issues.
On Mon, 2024-11-25 at 14:36 +0100, Jaroslav Škarvada wrote:
> the tcl package build started to fail with the same error in rawhide [1]:
> /usr/bin/find-debuginfo -j4 --strict-build
Hi Jeffrey,
On Wed, Nov 27, 2024 at 12:27:14PM -0500, Jeffrey Walton wrote:
> On Wed, Nov 27, 2024 at 11:35 AM Mark Wielaard wrote:
> > After lots of discussions at some of our Open Office hours, at the
> > Cauldron, with other Software Freedom organizations and some of our
&
ute
(security issues) back upstream. So any policies documenting how to
clearly report issues and documenting the contributing and release
practices should be helpful.
Please let us know if you have any questions or suggestions.
Cheers,
Mark Wielaard
(for the Sourceware PLC)
https://sourceware.org/mission.html#plc
1 - 100 of 5074 matches
Mail list logo
