all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ekaitz Zarraga <ekaitz@elenq.tech>,
	Pjotr Prins <pjotr.public12@thebird.nl>,
	Christopher Baines <mail@cbaines.net>,
	guix-devel@gnu.org
Subject: Re: RISCV porting effort
Date: Sun, 3 Jul 2022 12:07:24 +0300	[thread overview]
Message-ID: <YsFcTPH/fcophL2i@3900XT> (raw)
In-Reply-To: <87fsjm7434.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]

On Thu, Jun 30, 2022 at 02:01:19PM +0200, Ludovic Courtès wrote:
> Howdy,
> 
> Efraim Flashner <efraim@flashner.co.il> skribis:
> 
> > (ins)efraim@3900XT ~/workspace/guix$ time ./pre-inst-env guix weather -s riscv64-linux --substitute-urls="http://localhost:3000" -c100
> > computing 15,205 package derivations for riscv64-linux...
> > looking for 15,948 store items on http://localhost:3000...
> > http://localhost:3000
> >   14.3% substitutes available (2,274 out of 15,948)
> 
> Not bad!
> 
> Was it all built on a HiFive, or through emulated builds?

All on the HiFive. For some of the longer builds, like when I was
fiddling with llvm@9 and llvm@12 I emulated riscv64 on my machine so the
build was ~2 hours instead of ~6 hours, but after it built I garbage
collected it and rebuilt it on the native hardware.

> > Some notes:
> > * rust is definitely TODO
> > * GHC shouldn't be there on the list.
> > * gccgo should replace go@1.4. Currently I can't use gccgo@10 to build
> >   go@1.16.15, 1.17.9 or 1.17.11 on riscv64. gccgo@10 works for
> >   go@1.16.15 and 1.17.11.
> > * postgresql@13.6 I think is missing a patch currently
> > * libunwind isn't supported until 1.6.*
> > * valgrind isn't supported
> > * classpath@0.93 is the java bootstrap path
> > * openlibm, tbb and libunwind-julia are for julia
> > * node@10 doesn't (yet) recognize riscv64
> >
> > After that I don't remember offhand. I'm not sure I've tried yet to
> > build anything after ~170 so those can be ignored.
> 
> My guess is that upstream doesn’t go much further than you did, so
> thumbs up!

I just bumped libunwind on staging to 1.6.2 so that'll be available
eventually.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-07-03  9:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07  7:09 RISCV porting effort Efraim Flashner
2021-06-07 15:37 ` Christopher Lemmer Webber
2021-06-08 13:43 ` Ludovic Courtès
2021-06-08 22:28   ` Gabriel Wicki
2021-06-10 13:22     ` Efraim Flashner
2021-06-11 21:07     ` Ludovic Courtès
2021-06-10 13:20   ` Efraim Flashner
2021-06-11 22:07     ` Ludovic Courtès
2021-06-18 13:05     ` RISCV porting effort (now in stock @mouser) Gabriel Wicki
2021-06-11 11:16 ` RISCV porting effort Efraim Flashner
2021-06-13 17:24 ` Vagrant Cascadian
2021-06-14  7:27   ` Efraim Flashner
2021-06-15  1:00     ` Vagrant Cascadian
2021-06-15 12:37       ` Efraim Flashner
2021-06-13 21:21 ` Christopher Baines
2021-06-20 15:37   ` Ludovic Courtès
2022-06-16  1:46     ` Pjotr Prins
2022-06-16 18:12       ` Maxim Cournoyer
2022-06-17 16:08       ` Ludovic Courtès
2022-06-17 22:52         ` Pjotr Prins
2022-06-20  7:45           ` Pjotr Prins
2022-06-22 13:37             ` Ludovic Courtès
2022-06-22 15:19               ` Ekaitz Zarraga
2022-06-28  8:54                 ` Efraim Flashner
2022-06-30 12:01                   ` Ludovic Courtès
2022-07-03  9:07                     ` Efraim Flashner [this message]
2022-06-24  6:37               ` Pjotr Prins

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=YsFcTPH/fcophL2i@3900XT \
    --to=efraim@flashner.co.il \
    --cc=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=pjotr.public12@thebird.nl \
    /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.