On Sun, Sep 2, 2018 at 1:10 PM, 'Michael Clark' via RISC-V SW Dev
> Note to jimw: riscv-tools is not intended for compiling Linux distros. It’s
> the toolset that is a submodule of rocket-chip:
See the riscv-tools README.md file, which clearly talks about building
a linux system, and is hopelessly out of date. This is confusing
anyone that actually bothers to read the docs. There is also the
problem that no one is actively maintaining riscv-tools. The only
bugs that ever get fixed are show stopper bugs. I am well aware of
the fact that rocket-chip include riscv-tools. I've been told that
rocket-chip will be fixed to stop using riscv-tools. riscv-tools is
incidentally using an old obsolete gcc-7.2 which is known to be
broken. Anyone using riscv-tools for a compiler is making a serious
See also the software tools link on the riscv.org
home page which points at
which in turn points at riscv-tools and has instructions written in
Aug 2014 that also talk about building a linux system and that are
even more hopelessly out-of-date than the riscv-tools README.md file.
This is also confusing people that actually read the docs. We need to
rewrite this page and kill riscv-tools to fix this problem.
riscv-tools made sense 4 years ago when a small group was maintaining
everything and nothing was upstream. Nowadays it is a disaster, tools
maintained by different people with different ideas about how to
maintain tools and different levels of interest in maintaining the old
riscv-* repos versus the upstream repos which means there is no longer
any consistency in riscv-tools. There is also no need for it anymore.
rocket-chip should not be hard wired to a single compiler version.
Also, note that riscv-tools used to contain riscv-llvm, but the LLVM
maintainers completely stopped maintaining the riscv-llvm tree, and it
was so badly broken that we had no choice but to remove it. The
riscv-gnu-toolchain tree is still maintained, but for how long is
unknown. At some point, it probably makes more sense to start
supporting stable RISC-V branches in the FSF trees instead of
riscv-gnu-toolchain, like Linaro does. Most people know to look at
the FSF trees to find the GNU toolchain sources. And to look at the
LLVM trees to find the LLVM toolchain sources. Only RISC-V insiders
know about and use our github trees.