From nobody Fri Nov 15 23:47:21 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 4Xqtx50Mnhz5djqf for ; Fri, 15 Nov 2024 23:47:37 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xqtx41lZDz42B2 for ; Fri, 15 Nov 2024 23:47:36 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.221.42 as permitted sender) smtp.mailfrom=asomers@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none) Received: by mail-wr1-f42.google.com with SMTP id ffacd0b85a97d-38232c6311fso234484f8f.3 for ; Fri, 15 Nov 2024 15:47:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731714453; x=1732319253; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=eIMoTUPhSlwMnDkTCKGESR0qYZXYePSbTVvgxqTGNc0=; b=RiF4tSklShIbkHGzRYzuwohEN7UAfduRs6F/jOyKUz+rJ993i0ub5zXeoTlvyyDpKj JLPSz0f8zwTnkoYhSqHt0qgvYK74tUzCh+7Xc+gDY9uMizMhXt3uhvoy8Sa/nhUrAud5 W5xLrVlxGeq225TLmXNQ28w5EnimgOqavUhxneMVl7e22iQoQhh4mGQzLSZODOHpD2VU G5K0SxBJw3qwiSHjWGO+DCY/xEmOR7IK62tyz2ms/Jv3cgOHZfhjenel1kPqjvwBjsuS Yjie8PqrzCw1OZ3u2U+eWtNCZ6S/CbYjaFQL+Ze9Lg306BGRocXhQaImvgqp0fSKgvG4 8DQA== X-Gm-Message-State: AOJu0YyN1vCsBJrzVv8iYI31Rkh4wj7M2lkALJUKwGtllOnH7/cERklj CCK0WFkmbk7USzt3BdRGRX09SdCPoIGLLLXhshGY/5V5AP5bVKhoBoSbF/xypIDD2IYi4nvX+12 rwKakVYXgH4E47k+dcISPwgE12GC20Hk0 X-Google-Smtp-Source: AGHT+IGbbmhAokwTMNfIMH1xCbxzo95kqPyitwe67RmFWlpOT2mFrKzPEWgYjRo6vzerNMuwvEvNiqn4XwZig3mWKZ0= X-Received: by 2002:a5d:47a1:0:b0:381:df72:52cd with SMTP id ffacd0b85a97d-38225a0c616mr3101031f8f.23.1731714452939; Fri, 15 Nov 2024 15:47:32 -0800 (PST) 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 From: Alan Somers Date: Fri, 15 Nov 2024 16:47:21 -0700 Message-ID: Subject: Help wanted improving Rust support for RISC-V To: freebsd-riscv@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-2.84 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.993]; NEURAL_HAM_SHORT(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.96)[-0.958]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-riscv@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; FREEFALL_USER(0.00)[asomers]; MLMMJ_DEST(0.00)[freebsd-riscv@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.221.42:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.221.42:from] X-Rspamd-Queue-Id: 4Xqtx41lZDz42B2 X-Spamd-Bar: -- 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 only. * 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? -Alan [^1]: https://labs.scaleway.com/en/em-rv1/ [^2]: https://www.phoronix.com/review/scaleway-risc-v-cloud