From nobody Sat Nov 16 09:21:13 2024 X-Original-To: freebsd-riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xr7gM4vLjz5d5GQ for ; Sat, 16 Nov 2024 09:21:35 +0000 (UTC) (envelope-from thj@freebsd.org) Received: from fout-b6-smtp.messagingengine.com (fout-b6-smtp.messagingengine.com [202.12.124.149]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xr7gM1RpLz4rGQ; Sat, 16 Nov 2024 09:21:35 +0000 (UTC) (envelope-from thj@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.stl.internal (Postfix) with ESMTP id BB71B114014D; Sat, 16 Nov 2024 04:21:33 -0500 (EST) Received: from phl-imap-07 ([10.202.2.97]) by phl-compute-02.internal (MEProxy); Sat, 16 Nov 2024 04:21:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1731748893; x=1731835293; bh=t 1x+bghOuhDWHHZT5KdM/xTxFH6nyyeEydMCtUo2u3Q=; b=VXXIhdLKb+GGYDcP6 PiJts1HAC/scgvfWEAooQI5NL7xga14TYP4CWbAU+if95eUhaKesP489LAzYM6nu 42YKZcK44DTptn4IpsgdtFd6kHn0q3DyKIitinDG9dKEiWDeIIL56NdrA/A/I8Os s3uav/xBQO/rxRaoe1/dadF3qEZ7k65dPoawafu0UARhm9Kg8W3Z2Ul9F4FHksts seJyt8UmW/n391aIkk41dI2oCg6RMM+U7Cm2EAuLn3oWUFy4313kOMBItg7BXME0 TkjQJ4uvcxwLcsJXl+nODCY3NccKBPTdcgaf13CxS9IQsCS4lRKE0b7fr4RTQ89t 93H6w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrvdeigddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefoggffhffvkfgjfhfutgfgsehtqhertdertdejnecu hfhrohhmpedfvfhomhculfhonhgvshdfuceothhhjhesfhhrvggvsghsugdrohhrgheqne cuggftrfgrthhtvghrnhepveehjeffudehgeetkeeuteegtdetffffkedtveelheffledu veefieeutddutdejnecuffhomhgrihhnpegrughvvghnthhurhhishhtrdhmvgenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhjsehfrhgv vggsshgurdhorhhgpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprh gtphhtthhopegrshhomhgvrhhssehfrhgvvggsshgurdhorhhgpdhrtghpthhtohepfhhr vggvsghsugdqrhhishgtvhesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: ib75146ab:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 61CF8BA006F; Sat, 16 Nov 2024 04:21:33 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-riscv@freebsd.org Sender: owner-freebsd-riscv@FreeBSD.org MIME-Version: 1.0 Date: Sat, 16 Nov 2024 09:21:13 +0000 From: "Tom Jones" To: "Alan Somers" , freebsd-riscv@freebsd.org Message-Id: In-Reply-To: References: Subject: Re: Help wanted improving Rust support for RISC-V Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:151847, ipnet:202.12.124.0/24, country:AU] X-Rspamd-Queue-Id: 4Xr7gM1RpLz4rGQ X-Spamd-Bar: ---- On Fri, Nov 15, 2024, at 23:47, Alan Somers wrote: > I want to improve the state of Rust on FreeBSD in general, and RISC-V > in particular. My plan is: > > * Assemble a corpus of crates heavy on OS stuff (like Nix and Tokio) > and ensure that their tests pass on Riscv FreeBSD. > * Update libc's ABI to FreeBSD 12, finally eliminating the need for > COMPAT_11 on riscv to run Rust programs. > * Ensure that the corpus of crates still passes their tests. > * Convince the libc maintainers to use the FreeBSD 12 ABI, for riscv o= nly. > * After a full Rust release cycle (at least 6 weeks), and maybe two, > if there are no reports of breakage, and if Poudriere looks good, use > that as justification to raise libc's ABI for all architectures. > > But in order to do any of this, I need access to riscv hardware. A > virtual instance at Scaleway[^1][^2] would be ideal, but I don't know > if FreeBSD can run there. Has anybody tried it? Failing that, I > would need to either acquire some hardware myself, or borrow access to > somebody else's. Or, convince some other developer to do the work > himself. But I won't be able to help very much if I don't have direct > access. > > Can anybody on this list help me get some access? I can=E2=80=99t help with scaleway, it sounds like an interesting choice= .=20 I have no idea of the current state of easily and affordable available h= ardware. The visonfive 2 might be a good choice, there has been a lot of= work in the year since I last tried it.=20 https://adventurist.me/posts/00315 It=E2=80=99s probably still the easiest to get hold of if a little under= whelming.=20 You don=E2=80=99t mention qemu, is there some reason you can=E2=80=99t s= tart there? - Tom