'RISE' Project Building Open Source RISC-V Software Announced by Linux Foundation Europe

Linux Foundation Europe "has announced the RISC-V Software Ecosystem (RISE) Project to help facilitate more performant, commercial-ready software for the RISC-V processor architecture," reports Phoronix.

"Among the companies joining the RISE Project on their governing board are Andes, Google, Intel, Imagination Technologies, Mediatek, NVIDIA, Qualcomm, Red Hat, Rivos, Samsung, SiFive, T-Head, and Ventana."

It's top goal is "accelerate the development of open source software for RISC-V," according to the official RISE web site. The project's chair says it "brings together leaders with a shared sense of urgency to accelerate the RISC-V software ecosystem readiness in collaboration with RISC-V International." The CEO of RISC-V International, Calista Redmond, said "We are grateful to the thousands of engineers making upstream contributions and to the organizations coming together now to invest in tools and libraries in support of the RISC-V software ecosystem." RISE Project members will contribute financially and provide engineering talent to address specific software deliverables prioritized by the RISE Technical Steering Committee (TSC). RISE is dedicated to enabling a robust software ecosystem specifically for application processors that includes software development tools, virtualization support, language runtimes, Linux distribution integration, and system firmware, working upstream first with existing open source communities in accordance with open source best practices.

"The RISE Project is dedicated to enabling RISC-V in open source tools and libraries (e.g., LLVM, GCC, etc) to speed implementation and time-to-market," said Gabriele Columbro, General Manager of Linux Foundation Europe.
Google's director of engineering on Android said Google was "excited to partner with industry leaders to drive rapid maturity of the RISC-V software ecosystem in support of Android and more."

And the VP of system software at NVIDIA said "NVIDIA's accelerated computing platform — which includes GPUs, DPUs, chiplets, interconnects and software — will support the RISC-V open standard to help drive breakthroughs in data centers, and a wide range of industries, such as automotive, healthcare and robotics."

Shouldnt that be

[rossdee]

RVSE (RISC V Software Environment ) ?

GNU's not Unix

[andersh]

You don't have to name things using their initials.

No. Not really.

[Anonymous Coward]

RVSE (RISC V Software Environment ) ?

No. RVSE would be too hard to pronounce, and people would insert arbitrary vowel sounds to fix that, which would likely be inconsistent leading to confustion. Some would pronounce it "Riv-SEE," others "RAV-say," and still others, "reverse". Calling it "RISE" will probably cause fewer problems and less confusion. Most will likely pronounce it as if it rhymes with "ties," and a few will probably pronounce it as if the E were not silent, as "rye-suh," similar to the German word for a trip or voyage, "Reise

Re:

[account_deleted]

Comment removed based on user account deletion

Pay big $$ to play

[mtaht]

All these execs, and giant fees to join, and not a single actual open source developer on the boards. sigh At least LF hired linus....

Re:Pay big $$ to play

[algaeman]

I assume they are planning on contributing their work on LLVM and GCC into the upstream. Once the compilers are optimized for RISC-V, I think the vast majority of open source will just work.

How's this going to work with extensions

[smoot123]

I thought one of the features of the RISC-V architecture is it was easy to add processor extensions. But if I'm trying to create a Zypper archive of RISC-V binaries, how do I handle that? Do I compile for the base architecture? Some common extensions? Compile for whatever extension I want and use software emulation if that extension isn't present?

Or is this going to be a set of source-only distributions?

Re:

[tlhIngan]

I thought one of the features of the RISC-V architecture is it was easy to add processor extensions. But if I'm trying to create a Zypper archive of RISC-V binaries, how do I handle that? Do I compile for the base architecture? Some common extensions? Compile for whatever extension I want and use software emulation if that extension isn't present?

Or is this going to be a set of source-only distributions?

Well, it's open source, so yes, you'd just distribute the source code and let the compilers handle it.

It'

Re:

[smoot123]

Well, it's open source, so yes, you'd just distribute the source code and let the compilers handle it.

Gotta say, that's one of the things I don't miss from the '90s and '00s: building open source packages from source. Yes, configure is great. It's still a pain to unpack a tarball, run configure, build it, rebuild it because I got the --with-XXX and --without-YYY flags wrong, and install it.

"apt/yum/zypper/pip install XXX" is so much easier. It's nice to be able to get the source but 99% of the time, I'm just trying to remove a roadblock so I can get my real job done.

Translation: Corporations fed up with paying...

[ffkom]

... the "ARM instruction-set tax", aim at establishing some competition. (Which is kind of ironic given how much the same corporations totally want monopolies in their own respective businesses.)