https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #86 from Mark Wielaard ---
(In reply to Andreas Schwab from comment #84)
> Created attachment 179112 [details]
> riscv64: Avoid warning about missing return value in stat wrapper
Thanks, looks correct. Pushed as:
commit c2138bcb4ccb6d805e1
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #85 from Andreas Schwab ---
An implementation of the riscv_hwprobe syscall (258) is missing, which is used
by glibc to implement IFUNC.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #84 from Andreas Schwab ---
Created attachment 179112
--> https://bugs.kde.org/attachment.cgi?id=179112&action=edit
riscv64: Avoid warning about missing return value in stat wrapper
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #46 from Richard Jones ---
(In reply to Mark Wielaard from comment #43)
> Assuming fence and fence.tso are basically the same thing
> (which they might not be) then the following seems to fix it:
Normal memory model is Arm-like (ie. quite r
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=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 in glibc strcmp_unaligned_l
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,
fsconfig, fs
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
> the risc-v
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_HI20
collect2:
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"?
> >
> > > memcheck/tests/sh-mem-random
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
Jure Repinc changed:
What|Removed |Added
CC||j...@holodeck1.com
--
You are receiving this mai
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 instruction
tests by "a1".
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);
TESTINST_0_2_Bxx_COND def
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 neede
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_thread_fence (__ATOMIC_ACQ
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 checks
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.
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #62 from Paul Floyd ---
(In reply to Mark Wielaard from comment #60)
> (In reply to Mark Wielaard from comment #55)
> > nestedfns fails with:
> >
> > +Process terminating with default action of signal 11 (SIGSEGV)
> > + Bad permissions for
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.
> This one is
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
> + at 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 using unsigned int and
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 fail
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
compressed compresse
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 fa
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 one is
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 +1161
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 should
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #51 from Paul Floyd ---
Everything is OK on FreeBSD.
--
You are receiving this mail because:
You are watching all bug changes.
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 a repo with
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #49 from Paul Floyd ---
(In reply to Mark Wielaard from comment #44)
> So it isn't immediately clear why it tries to find the stack_cache_actsize
> var in libpthread.so.0
--sim-hints=no-nptl-pthread-stackcache controls this. If that is set
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #48 from Richard Jones ---
That'll be fine in that case!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #47 from Paul Floyd ---
(In reply to Richard Jones from comment #46)
> Does valgrind have anything like Arm vs x86 memory models? If it does then
> I suspect the above will be wrong.
I don't think that the memory models really matter. Val
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #45 from Richard Jones ---
(In reply to Mark Wielaard from comment #35)
> integer.c:132: Error: illegal operands `la zero,0'
Are you maintaining these patches in a git repo somewhere? It might be easier
to follow that way. I can't find th
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): unhandled instruction 0x
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 be disabl
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
--- a/cor
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
inde
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 int and
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/m
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)
hel
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/configure.ac
+++
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 -I. -I../../.. -I../../..
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 a
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/helgri
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 file
descrip
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|
https://bugs.kde.org/show_bug.cgi?id=468575
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #24 from Paul Floyd ---
(In reply to JojoR from comment #23)
> Hi, Paul Floyd & Petr Pavlu
>
> Any progress ?
> It's depression if there are a few small issues :(
There are two things that I consider as requirements.
Firstly someone to g
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #23 from JojoR ---
Hi, Paul Floyd & Petr Pavlu
Any progress ?
It's depression if there are a few small issues :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #22 from JojoR ---
> > [...]
> > none/tests/riscv64/compressed(stdout)
> > none/tests/riscv64/compressed(stderr)
> > none/tests/riscv64/integer (stdout)
> > none/tests/riscv64/integer (stde
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #21 from Petr Pavlu ---
(In reply to Paul Floyd from comment #20)
> And regtest results
>
> == 737 tests, 6 stderr failures, 2 stdout failures, 0 stderrB failures, 1
> stdoutB failure, 0 post failures ==
> gdbserver_tests/hgtls
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=468575
--- Comment #19 from JojoR ---
(In reply to Paul Floyd from comment #18)
> 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-protecto
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
compressed
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=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 b
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #15 from JojoR ---
(In reply to Paul Floyd from comment #14)
> 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/
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). I'
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #13 from JojoR ---
@Paul Floyd
Has anyone reviewed these patches ?
It has taken long time and there is not any feedback :)
Could we review & push these basic ISAs (rv64gc) implementation first ?
other of extensions like Vector of RISCV de
https://bugs.kde.org/show_bug.cgi?id=468575
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=468575
Richard Jones changed:
What|Removed |Added
CC||rjo...@redhat.com
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=468575
la...@foxmail.com changed:
What|Removed |Added
CC||la...@foxmail.com
--- Comment #12 from la...
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #11 from JojoR ---
@Paul Floyd
Has anyone reviewed these patches ?
It has taken two months and there is not any feedback :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
JojoR changed:
What|Removed |Added
CC||rjie...@gmail.com
--- Comment #10 from JojoR ---
(In r
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #9 from Petr Pavlu ---
(In reply to Paul Floyd from comment #8)
> hginfo fails on several systems
> TLS is, well, tricky
>
> Are the other failures "reaonable"?
The following is a short summary why the remaining tests fail. However, I'm no
https://bugs.kde.org/show_bug.cgi?id=468575
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #8 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #7 from Petr Pavlu ---
v1:
* attachment 158147 [details] v1-0001-riscv64-valgrind-new.patch,
* attachment 158148 [details] v1-0002-riscv64-vex-new.patch,
* attachment 158149 [details] v1-0003-riscv64-tests-new.patch,
* attachment 158150 [det
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #6 from Petr Pavlu ---
Created attachment 158152
--> https://bugs.kde.org/attachment.cgi?id=158152&action=edit
v1-0006-riscv64-tests-mod.patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #5 from Petr Pavlu ---
Created attachment 158151
--> https://bugs.kde.org/attachment.cgi?id=158151&action=edit
v1-0005-riscv64-vex-mod.patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #4 from Petr Pavlu ---
Created attachment 158150
--> https://bugs.kde.org/attachment.cgi?id=158150&action=edit
v1-0004-riscv64-valgrind-mod.patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #3 from Petr Pavlu ---
Created attachment 158149
--> https://bugs.kde.org/attachment.cgi?id=158149&action=edit
v1-0003-riscv64-tests-new.patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #2 from Petr Pavlu ---
Created attachment 158148
--> https://bugs.kde.org/attachment.cgi?id=158148&action=edit
v1-0002-riscv64-vex-new.patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #1 from Petr Pavlu ---
Created attachment 158147
--> https://bugs.kde.org/attachment.cgi?id=158147&action=edit
v1-0001-riscv64-valgrind-new.patch
--
You are receiving this mail because:
You are watching all bug changes.
90 matches
Mail list logo
