Age | Commit message (Collapse) | Author | Files | Lines |
|
Add --with-extra-multilib-test option
|
|
Signed-off-by: cy023 <cyyang023@gmail.com>
|
|
NOTE: This is toolchain developer facing feature.
This allow user to add extra testing multi-lib arch, it's useful when
develop and/or testing new extensions.
Usage:
--with-extra-multilib-test="arch-abi[;arch-abi]"
e.g.
linux enable enabled multilib, so default will build with follwoing
configuration:
lib32/ilp32;@march=rv32imac@mabi=ilp32
lib32/ilp32d;@march=rv32imafdc@mabi=ilp32d
lib64/lp64;@march=rv64imac@mabi=lp64
lib64/lp64d;@march=rv64imafdc@mabi=lp64d
But you want to testing more on vector stuffs like rv32gcv and rv64gcv,
then you can configure with `--with-extra-multilib-test="rv32gcv-ilp32d;rv64gcv;lp64d"`
Then the testing will run rv32imac-ilp32 rv32imafdc-ilp32d
rv64imac-lp64 rv64imafdc-lp64d and rv32gcv-ilp32d;rv64gcv;lp64d!
NOTE: Extra multilib test settings still require existing
multilib has support those extra settings, e.g. you can't add
rv32imafc_zbb-ilp32f on above example since no compatible multilib has
provided.
|
|
Update readme about newlib toolchain flow
Co-authored-by: Yun Hsiang <yun.hsiang@sifive.com>
|
|
|
|
|
|
Update readme about llvm & qemu examples
Co-authored-by: Kito Cheng <kito.cheng@sifive.com>
|
|
We currently have a stale "llvm" branch, that does not build.
However, there is clear demand in the RISC-V toolchain community
for a working LLVM on top of a recent GNU toolchain.
In order to build such a toolchain, quite some LLVM and clang know-how is
required to avoid path issues at LLVM build time or later when using clang.
The main purpose of this commit is to demonstrate a way to combine
the RISC-V GNU toolchain repo with LLVM, with the intent to save
others hours of frustration, debugging time or support time.
Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
|
|
ubuntu20.04 make it need "clang ninja-build"
Signed-off-by: 长柳 <110147328+changliuxy@users.noreply.github.com>
|
|
Let's document how to use the environment variable RUNTESTFLAGS
for selecting the tests that should be executed.
Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
|
|
Let's document how to run all the test suites in order to increase the
number of people that will execute the tests.
Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
|
|
|
|
|
|
Add --with-isa-spec option to configure
|
|
Set the default version to 2.2 for now, and once we bump to GCC 12 we
will bump that to 20191213.
|
|
The upstream musl libc does not support 32bit RISC-V builds.
We therefore only allow building the 64bit version (i.e.,
riscv64-unknown-linux-musl-).
Signed-off-by: Florian Hofhammer <florian.hofhammer@fhofhammer.de>
|
|
Signed-off-by: Florian Hofhammer <florian.hofhammer@fhofhammer.de>
|
|
This patch introduces a configure-time source-dir override for QEMU
similar to the existing overrides for the other toolchain sources.
Signed-off-by: Christoph Muellner <cmuellner@linux.com>
|
|
Just updating previous PR as `mpc` is a music player, `libmpc` is the correct required package.
|
|
[https://aur.archlinux.org/packages/riscv-gnu-toolchain/](https://aur.archlinux.org/packages/riscv-gnu-toolchain/)
Added:
Also available for Arch users on the AUR: [https://aur.archlinux.org/packages/riscv-gnu-toolchain/](https://aur.archlinux.org/packages/riscv-gnu-toolchain/)
|
|
|
|
|
|
|
|
|
|
The current README.md only explains how to use multilib on the Linux cross-compiler, but not on the Newlib one. This might create confusion as seen here https://github.com/riscv/riscv-tools/issues/287, or makes it seem like you can't multilib on Newlib. It's also the case that the multilib option is more common on embedded toolchains rather than on Linux, so I believe this small change on documentation should clear things up.
|
|
|
|
|
|
|
|
|
|
Added dependencies for Arch Linux
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add BINUTILS_GDB_TARGET_FLAGS, init to --with-expat=yes, and pass to all 3 gdb
configure commands. Update README.md to list expat package names.
|
|
https://github.com/riscv/riscv-gnu-toolchain/issues/296
|
|
Fixes: https://github.com/riscv/riscv-gnu-toolchain/issues/286
|
|
|
|
|
|
|
|
|
|
|
|
github requires 4 spaces before a block to make it produce code blocks.
|
|
|
|
|
|
|
|
Without g++, it fails in this rather opaque way:
configure: error: error verifying int64_t uses long long
Makefile:4063: recipe for target 'configure-gcc' failed
make[2]: *** [configure-gcc] Error 1
make[2]: Leaving directory '/tmp/riscv-gnu-toolchain/build-gcc-newlib'
Makefile:867: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/tmp/riscv-gnu-toolchain/build-gcc-newlib'
Makefile:245: recipe for target 'stamps/build-gcc-newlib' failed
make: *** [stamps/build-gcc-newlib] Error 2
|
|
|