9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: [9fans] riscv toolchain update
Date: Mon, 9 Nov 2020 16:34:11 +0000	[thread overview]
Message-ID: <cca09d17328027246734517ec25c8f7a@hamnavoe.com> (raw)

There's an updated RISC-V compiler (plus assembler, linker, libmach and
other library additions, etc) in contrib/miller/riscv.tar on 9p.io 

The original release was just for the simple rv32i instruction set. It's now
expanded to full rv32gc and rv64gc support, including floating point (single
and double) and compressed instructions. Instruction compression is done
automatically by default in the linker; use the option '-c' if you want to
disable it. (Compressed instructions generally run faster in hardware but
slower in emulation.)

Because of a collision with my original choice of architecture letter, it's
been changed to 'i' for riscv and 'j' for riscv32. This does unfortunately
introduce a new collision: suffix '.i' was used historically for some firmware
files (etherm10g[24]k.i, sd53c8xx.i and uartaxp.i) in the pc kernel. These
will be erroneously identified as object files after the riscv update, so
'mk clean' in /sys/src/9/pc would delete them. The files are actually C
source code referenced in #include statements, so a straightforward solution
is to rename them from '.i' to '.h', and apply patch/pc-rename-i-suffix on 9p.io
which will correct the relevant #include statements.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4943bad991203d32-Md8b063389a49362009cdea13
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

             reply	other threads:[~2020-11-09 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 16:34 Richard Miller [this message]
2020-11-13 23:26 ` Pouya Tafti

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=cca09d17328027246734517ec25c8f7a@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@9fans.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).