Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
s-macke
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
41 ms
·
451.
▲
by
s-macke
13y ago
Yes, the asm.js code is written by hand. Took around one day. What happened with Firefox I don't know. Firefox 22 was fast (above 30 MIPS) and then it dropped. No chance to find the problem. Chrome sometimes thinks that integers are
452.
▲
by
s-macke
13y ago
I made the same experience with my hand optimized asm.js code. http://s-macke.github.io/jor1k/ It runs as fast as asm.js in Firefox. Chrome is optimizing it really well.
453.
▲
by
s-macke
13y ago
And again. We had the news about the same emulator one month ago, but without X and Wayland. But of course I like it :) Believe me or not. The hard part was not to write the emulator. The CPU needs less than 1000 lines of code. No, the ha
454.
▲
by
s-macke
13y ago
Sound good. Websockets are the best solution I suppose. If you need help you can find me in the #openrisc chat at chat.freenode.net .
455.
▲
by
s-macke
13y ago
This features sound like fun. But networking is not on my priority list right now. Problem is the server and security issues. At the moment everything runs out of the box even on the simplest web server. This would change. And at the moment
456.
▲
by
s-macke
13y ago
The toolchain (uCluibc development) I am using is explained here http://opencores.org/or1k/OpenRISC_GNU_tool_chain My scripts for the toolchain are published here: https://github.com/s-macke/jor1k-
457.
▲
by
s-macke
13y ago
Yes, I thought about it. The DOM manipulation and the hardware emulation is separated. Unfortunately with the implementation of worker threads it became more complicated to run this code in headless v8.
458.
▲
by
s-macke
13y ago
http://simulationcorner.net/X11.png I am working on it. But it is extremely unstable. In the picture you see the best shot I ever got.
459.
▲
by
s-macke
13y ago
Editor: Normal text editor with syntax highlightning Testing: Firefox and Chrome Debugging: Function console.log Optimization: JIT inspector for Firefox (incompatible since FF 23) and profiling tools from both browsers So, nothing special i
460.
▲
by
s-macke
13y ago
Yes, programmed the asm.js core by hand. It was not too hard. One day. The asm.js is also a little bit outdated. It could be around 20% faster. I have never used the standalone asm.js validator. Not even knew, that it exists. The optimizing
461.
▲
by
s-macke
13y ago
Corrected, should be available soon. https://github.com/s-macke/jor1k/commit/1285da3247a1a92f6638...
462.
▲
by
s-macke
13y ago
As written in the wiki, Firefox 23 is at the moment not a good choice. Firefox 22 emulates this machine three times faster and possibly Firefox 24 will return to this peak. Chrome is fine.