Hi Nicolas, On Tue, Dec 9, 2014 at 10:59 PM, Nicolas B. Pierron <[email protected]> wrote: > On 12/06/2014 02:23 PM, Xue Fuqiao wrote: >> >> * ES6 (and TC-39, and the standardization process) > > I am not the right person to talk to, but I am sure other person on this > mailing list can give you some pointers.
I see. Thank you. (BTW, I forgot to mention ES7.) > We do not have a long documentation of the internals of the JavaScript > engine, but you can have a look at the "Tips, tricks and philosophy" section > of the following page: > > https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey > > You can find the documentation of the bytecode in the source: > > http://dxr.mozilla.org/mozilla-central/source/js/src/vm/Opcodes.h#84 > > The Jit are located in js/src/jit, and asmjs is located in js/src/asmjs. Since I do not familiar with {interpreters, compilers, garbage collectors}, I need to learn the concepts (like machine language, VM, scanning/parsing, code generation/optimization and mark-and-sweep GC) first to be able to understand these pages. Do you have any learning material to recommend? I'm reading the pages on Wikipedia now, but some articles seems to be too technical for me now. >> * JS engine benchmarking (Kraken/SunSpider/Octane) > > The easiest way is to build the shell, and to use arewefastyet sources to > run it on your computer. > > https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Hacking_Tips#Benchmarking_%28shell%29 > >> * Make (I can only write some very simple rules.) > > Don't worry, we rarely have to add new files, and even though, we rarely > have to add new compilation rules. > >> * Security > > This is the kind of things that you learn in due time, after having > contributed for a while. OK, thanks! > Don't worry, if there is anything to learn, you will learn it in time, you > should not worry about making mistakes, the mentors / reviewers are here to > guide you through and to fix things behind you if you are not around. > > If you don't know where to start, you can have a look at a few bugs which > have been registered as mentored: > > http://www.joshmatthews.net/bugsahoy/?jseng=1&unowned=1 > > Usually, I assign bugs as soon as there is a reasonable patch to claim that > somebody is working on the bug. So feel free to take any bug with no > activity, and mention that you want to start working on it ;) OK. I've started learning/contributing by reading/editing the pages about SpiderMonkey on MDN[1]. [1] https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Internals$history _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
