riscv-gcc
riscv-gnu-toolchain
riscv-gcc | riscv-gnu-toolchain | |
---|---|---|
3 | 35 | |
359 | 3,187 | |
- | 4.2% | |
0.0 | 8.2 | |
almost 1 year ago | 8 days ago | |
C | ||
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
riscv-gcc
-
How to extend Risc-V P extension in riscv-gcc and riscv-binutils?
gcc: https://github.com/riscv-collab/riscv-gcc/pull/258
-
riscv64-unknown-elf-objdump
It does not appear to have been packaged in fedora from what I can tell. You could try to build it from source. https://github.com/riscv-collab/riscv-gcc
- Sipeed tease new Allwinner D1 board
riscv-gnu-toolchain
-
Is RISC-V ready for HPC? Evaluating the 64-core Sophon SG2042 RISC-V CPU
> no absurdely and grotesquely massive and complex compilers anywhere
Absence of evidence is not evidence of absence, and anyway there's not even an absence: https://github.com/riscv-collab/riscv-gnu-toolchain https://llvm.org/docs/RISCVUsage.html
> feature creeps on computer language syntax nowhere to be found
At least one of us is very confused, and in case it's me, how do language details matter to RISC-V?
-
Help trying to build for riscv64gc-unknown-linux-musl
I then looked at the .cargo/config.toml provided by the guide and saw that it wasn't actually statically compiling the code. After a bit of tinkering and building my own toolchain from here, I ended up with this config.toml file:
- GNU toolchain for RISC-V including GCC
-
Building a toolchain suitable for compiling V extension code
b) collabriscv - essentially gcc 12.2 + binutils master/2.40 as per https://github.com/riscv-collab/riscv-gnu-toolchain
- How do i specify vendor name while building the GNU toolchain?
-
GCC 13 Adds RISC-V T-Head Vendor Extension Collection
Or would it be better to take what is in https://github.com/riscv-collab/riscv-gnu-toolchain which is gcc 12.2 and start from there?
-
How to build toolchain with Zbs extension?
I'm not able to build https://github.com/riscv-collab/riscv-gnu-toolchain.git like this:
What are some alternatives?
rvv-llvm - This repository is outdated, support for RISC-V is now developed in upstream LLVM
riscv-binutils-gdb - RISC-V backports for binutils-gdb. Development is done upstream at the FSF.
risc-v-examples - RISC-V examples for GD32V, K210, and QEMU
riscv-opcodes - RISC-V Opcodes
binutils-gdb
buildroot - Buildroot, making embedded Linux easy. Note that this is not the official repository, but only a mirror. The official Git repository is at http://git.buildroot.net/buildroot/. Do not open issues or file pull requests here.
riscv-binutils-devmemo - binutils development memo (for RISC-V)
freedom-tools - Tools for SiFive's Freedom Platform
xv6-riscv - Xv6 for RISC-V
riscv-v-spec - Working draft of the proposed RISC-V V vector extension