search

rmcilroy / octane-benchmark

Automatically exported from code.google.com/p/octane-benchmark
0 stars 0 forks source link

Possible inclusion of 1964js cpu core #8

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
1964js is a Nintendo 64 emulator that converts MIPS code to Javascript and then 
uses it to emulate games. While the emulator does use WebGL for displaying 
graphics, it does not use it for the CPU. This benchmark would be CPU intensive 
especially later on, when the core is more complete.

Original issue reported on code.google.com by kevo...@gmail.com on 13 Sep 2012 at 8:07

GoogleCodeExporter commented 9 years ago 
There is also n64js, which is in a semi-usable state, but ROM loading would 
have to be automated.

Original comment by kevo...@gmail.com on 13 Sep 2012 at 8:24

GoogleCodeExporter commented 9 years ago 
They might be looking for a 100% js implementation that doesn't rely on 
hardware acceleration. That might be a possible reason they went with 
gameboy-online (It renders the image in js directly, only uses canvas functions 
for scaling and blit).

Original comment by grantgal...@gmail.com on 21 Sep 2012 at 2:55

GoogleCodeExporter commented 9 years ago 
They went with a dummy canvas object for gb-emu, so that might answer the 
question on canvas support here.

Original comment by grantgal...@gmail.com on 21 Sep 2012 at 2:56

GoogleCodeExporter commented 9 years ago 
At this rate, someone might propose including jslinux in here. :P

Original comment by grantgal...@gmail.com on 21 Sep 2012 at 2:58

GoogleCodeExporter commented 9 years ago 
As correctly pointed out in #2, only headless tests make sense since it needs 
to be able to run on the bare javascript engine.

Original comment by yangguo@chromium.org on 11 Dec 2012 at 2:42