News for hackers. Stuff that matters.
Re:RISC-V port submitted for inclusion in GCC by jordskott on Thursday January 12, 2017 @06:56AM (#13381562)
Re:RISC-V port submitted for inclusion in GCC by e19293001 on Thursday January 12, 2017 @08:55AM (#13382162)
I agree with what was said from your links. The code was poorly written but that does not mean that this can't be improved once they get an active community. Sadly, right now they are inactive and I don't know why.
Re:RISC-V port submitted for inclusion in GCC by TD-Linux on Thursday January 12, 2017 @08:53AM (#13382147)
I think the complaints about peripheral source are valid, but they have had it running on silicon for months, so the answer to "will it work" is pretty clear.
Re:RISC-V port submitted for inclusion in GCC by jokr004 on Friday January 13, 2017 @11:02AM (#13391786)
"First of all, it is just a simple microcontroller and the implemented RISC-V instructions are not that significant for the purpose. It's like expecting the SIM cards used in mobile phones to be equivalent to PCs because they run "Java"."

Who is calling this a PC? OpenV seems to be marketing itself as a microcontroller, it keeps comparing itself to Arduino.

Re:RISC-V port submitted for inclusion in GCC by bostand on Thursday January 12, 2017 @07:39AM (#13381738)
These are very valid concerns.

I should also add that the "boring" mips is right now significantly more open than riscv, more mature and easier to get hold of.

Re:RISC-V port submitted for inclusion in GCC by Narishma on Thursday January 12, 2017 @08:10AM (#13381898)
His concerns are with OpenV, not RISC-V.