Linked by Thom Holwerda on Wed 29th Aug 2018 22:03 UTC
Hardware, Embedded Systems

Developed in a magic night of 19 Aug, 2018 between 2am and 8am, the darkriscv is a very experimental implementation of the opensource RISC-V instruction set. Nowadays, after one week of exciting sleepless nights of work (which explains the lots of typos you will found ahead), the darkriscv reached a very good quality result, in a way that the "hello world" compiled by the standard riscv-elf-gcc is working fine!

I feel incompetent.

E-mail Print r 5   5 Comment(s)
Order by: Score:
don't feel bad, Thom
by gus3 on Thu 30th Aug 2018 00:56 UTC
gus3
Member since:
2010-09-02

It only took me >25 years to understand the Turing Machine and Turing-equivalence.

Reply Score: 3

v RE: don't feel bad, Thom
by Dr.Cyber on Thu 30th Aug 2018 10:42 UTC in reply to "don't feel bad, Thom"
RE: don't feel bad, Thom
by Brendan on Thu 30th Aug 2018 13:27 UTC in reply to "don't feel bad, Thom"
Brendan Member since:
2005-11-16

Hi,

It only took me >25 years to understand the Turing Machine and Turing-equivalence.


No! Apparently, you don't count most of the time spent developing something as "development time".

Darkriscv was "developed" in 6 hours, and then took at least a week of fixing all the problems and changing it just to make it work for the simplest "hello world" program, and has been constantly worked on for a fortnight now, and will probably take 5 more years of "not development" before it's finished being "developed in 6 hours".

In the same way; you probably "developed" your understanding of turing machines in 2 seconds and then spent 25 years fixing all the problems and changing it. ;-)

- Brendan

Reply Score: 6

v RE[2]: don't feel bad, Thom
by Dr.Cyber on Thu 30th Aug 2018 16:41 UTC in reply to "RE: don't feel bad, Thom"
RE[2]: don't feel bad, Thom
by oiaohm on Fri 31st Aug 2018 09:00 UTC in reply to "RE: don't feel bad, Thom"
oiaohm Member since:
2009-05-30

Also Darkriscv is done the hard way in verilog


There is quite a bit of difference doing a design using
https://chisel.eecs.berkeley.edu/ with SLSV and UVM.

It is possible to do a RV32I using those tools with development and testing time to fully functional in 2 work days 16 hours working of course computers running through the night running the test suites finding everywhere you have goofed it.

The time fixing with the darkriscv you would blame on not really using the best tools for the job and lack of resources.

Reply Score: 3