You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -91,7 +91,7 @@ To build either cross-compiler with support for both 32-bit and
91
91
64-bit, run the following command:
92
92
93
93
./configure --prefix=/opt/riscv --enable-multilib
94
-
94
+
95
95
And then either `make`, `make linux` or `make musl` for the Newlib, Linux
96
96
glibc-based or Linux musl libc-based cross-compiler, respectively.
97
97
@@ -104,7 +104,7 @@ using the `--print-multi-lib` flag on either cross-compiler.
104
104
Linux toolchain has an additional option `--enable-default-pie` to control the
105
105
default PIE enablement for GCC, which is disable by default.
106
106
107
-
To customize the enabled languages, use option `--with-languages=`. For example,
107
+
To customize the enabled languages, use option `--with-languages=`. For example,
108
108
if you want to enable `c,c++,fortran`, use `./configure --with-languages=c,c++,fortran`.
109
109
This option only takes effect for the GNU toolchain.
110
110
@@ -218,8 +218,8 @@ This flag is particularly useful for developers testing and emulating full RISC-
218
218
The Dejagnu test suite has been ported to RISC-V. This can be run with a
219
219
simulator for the elf and linux toolchains. The simulator can be selected
220
220
by the SIM variable in the Makefile, e.g. SIM=qemu, SIM=gdb, or SIM=spike
221
-
(experimental).In addition, the simulator can also be selected with the
222
-
configure time option `--with-sim=`.However, the testsuite allowlist is
221
+
(experimental).In addition, the simulator can also be selected with the
222
+
configure time option `--with-sim=`.However, the testsuite allowlist is
223
223
only maintained for qemu.Other simulators might get extra failures.
224
224
225
225
#### Additional Prerequisite
@@ -279,12 +279,12 @@ that are being executed using the environment variable `RUNTESTFLAGS`.
279
279
To restrict a test run to only RISC-V specific tests
280
280
the following command can be used:
281
281
282
-
RUNTESTFLAGS="riscv.exp" make report
282
+
RUNTESTFLAGS="riscv.exp" make report
283
283
284
284
To restrict a test run to only RISC-V specific tests with match the
285
285
pattern "zb*.c" and "sm*.c" the following command can be used:
286
286
287
-
RUNTESTFLAGS="riscv.exp=zb*.c\ sm*.c" make report
287
+
RUNTESTFLAGS="riscv.exp=zb*.c\ sm*.c" make report
288
288
289
289
#### Testing GCC, Binutils, and glibc of a Linux toolchain
290
290
@@ -490,8 +490,8 @@ sources is among them. The flag `--enable-host-gcc` does exaclty that:
490
490
491
491
### FAQ
492
492
#### Ensuring Code Model Consistency
493
-
If parts of newlib are going to be replaced with an external library (such as with [libgloss-htif](https://github.com/ucb-bar/libgloss-htif) for Berkeley Host-Target Interface),
494
-
you should take care to ensure that both newlib and the external library are built using the same code model. For more information about RISC-V code models,
493
+
If parts of newlib are going to be replaced with an external library (such as with [libgloss-htif](https://github.com/ucb-bar/libgloss-htif) for Berkeley Host-Target Interface),
494
+
you should take care to ensure that both newlib and the external library are built using the same code model. For more information about RISC-V code models,
495
495
[read this SiFive blog article](https://www.sifive.com/blog/all-aboard-part-4-risc-v-code-models).
496
496
497
497
Errors that indicate a code model mismatch include "relocation overflow" or "relocation truncated" errors from the linker being unable to successfully relocate symbols in the executable.
0 commit comments