From: Arun Isaac <arunisaac@systemreboot.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Maxime Devos <maximedevos@telenet.be>, 54615-done@debbugs.gnu.org
Subject: [bug#54615] [PATCH v3 2/2] gnu: Add riscv-pk.
Date: Fri, 01 Apr 2022 12:02:54 +0530 [thread overview]
Message-ID: <87sfqx8ga1.fsf@systemreboot.net> (raw)
In-Reply-To: <YkWe4uCCZgPY35xB@3900XT>
> Thanks for the patches. Does it make sense to wrap spike with
> riscv-pk?
>
> I'm not sure how much spike is used without pk.
I see and feel your pain. :-P But, maybe it's best to not make that
assumption. I don't know enough about riscv-pk to say for sure.
The better solution may be for spike to look in $PATH when trying to run
a program. I have asked for this upstream:
https://github.com/riscv-software-src/riscv-isa-sim/issues/961
Thank you both for reviewing and merging these patches!
next prev parent reply other threads:[~2022-04-01 6:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 18:41 [bug#54615] [PATCH 0/2] Add riscv-pk and improve spike Arun Isaac
2022-03-28 18:43 ` [bug#54615] [PATCH 1/2] gnu: spike: Substitute path to dtc instead of wrapping executables Arun Isaac
2022-03-28 18:43 ` [bug#54615] [PATCH 2/2] gnu: Add riscv-pk Arun Isaac
2022-03-28 18:55 ` [bug#54615] [PATCH v2 0/2] Add riscv-pk and improve spike Arun Isaac
2022-03-28 18:55 ` [bug#54615] [PATCH v2 1/2] gnu: spike: Substitute path to dtc instead of wrapping executables Arun Isaac
2022-03-28 19:49 ` Maxime Devos
2022-03-29 10:42 ` Arun Isaac
2022-03-29 10:43 ` [bug#54615] [PATCH v3 " Arun Isaac
2022-03-29 10:43 ` [bug#54615] [PATCH v3 2/2] gnu: Add riscv-pk Arun Isaac
2022-03-31 12:30 ` bug#54615: " Efraim Flashner
2022-04-01 6:32 ` Arun Isaac [this message]
2022-03-28 18:55 ` [bug#54615] [PATCH v2 " Arun Isaac
2022-03-28 19:24 ` Maxime Devos
2022-03-28 20:10 ` [bug#54615] [PATCH v2 0/2] Add riscv-pk and improve spike Efraim Flashner
2022-03-29 10:39 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfqx8ga1.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=54615-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.