3 ms·

I am pretty excited about RISC-V. Hoping to see a v8 JavaScript and Node.js port in the future.

• thethirdone 8y ago
  That shouldn't be super hard. I don't think there is much assembly in either. And C can be compiled to RISC-V already. My only experience porting node was to a specialized ARM system a while ago, so ARM support may have been already built in or things may have changed. edit: as people have commented, there indeed is a fair amount of arch specific stuff for reference the mips directory https://github.com/v8/v8/tree/master/src/mips64 https://github.com/v8/v8/tree/master/src/mips64
  • comex 8y ago
    V8 has a JIT, which is always going to require work to port to a new architecture. But the new-ish TurboFan backend is supposed to have the architecture-dependent parts relatively well factored out[1], so it's not as hard as it might be. https://docs.google.com/presentation/d/1_eLlVzcj94_G4r9j9d_Lj5HRKFnq6jgpuPJtnmIBs88 https://docs.google.com/presentation/d/1_eLlVzcj94_G4r9j9d_L...
  • Matthias247 8y ago
    v8 is a JIT compiler. It emits instructions for specific architectures. So even if it's not written in assembly, it has some very architecture specific parts in it.
  • Iwan-Zotow 8y ago
    > I don't think there is much assembly in either. it has nothing to do with assembly, or ability to compile C it is basically typical compiler with front-end and back-end. While front-end is platform independent and could be ported easily, back-end usually takes quite some time to retarget for a different architecture