Tachyon-list Mai 2010

tachyon-list@iro.umontreal.ca

4 participants
19 discussions

Démarrer une nNouvelle discussion

Meeting Wed May 26th, 10am ?
by Erick Lavoie 11 Jui '10

11 Jui '10

I just want to confirm our meeting next Wednesday at 10am. Is it all right for everybody? Erick

5 38

Parser
by Marc Feeley 24 Mai '10

24 Mai '10

With Erick's help I have now made the first commit of the Javascript parser to the repository. I'd like everyone to take a look at the AST representation so that we can make adjustments earlier rather than later. The AST constructors are defined in file parser.js (search for the comment "// Constructors."). The file js.js has an AST pretty-printer which walks an AST recursively to show its content. It also gives location information for each node. If you install the emacs package "tachyon.el" (follow the instructions at the top of the file) then you can scroll through the pretty-printed AST to automatically highlight the corresponding source code (in a subwindow) simply by placing the cursor on the line with the location information. Here is a sample execution of the parser on the file: function f(x) { if (x < 2) return 1; else return f(x-1) + f(x-2); } % cd parser % ./js tests/test1.js Program ("tests/test1.js"@1.1-7.2:) |-statements= | FunctionDeclaration ("tests/test1.js"@1.1-7.2:) | |-id= f | |-params= x | |-body= | | IfStatement ("tests/test1.js"@3.5-6.32:) | | |-expr= | | | OpExpr ("tests/test1.js"@3.9-3.14:) | | | |-op= "x < y" | | | |-exprs= | | | | Var ("tests/test1.js"@3.9-3.10:) | | | | |-id= x | | | | Literal ("tests/test1.js"@3.13-3.14:) | | | | |-value= 2 | | |-statements= | | | ReturnStatement ("tests/test1.js"@4.9-4.18:) | | | |-expr= | | | | Literal ("tests/test1.js"@4.16-4.17:) | | | | |-value= 1 | | | ReturnStatement ("tests/test1.js"@6.9-6.32:) | | | |-expr= | | | | OpExpr ("tests/test1.js"@6.16-6.31:) | | | | |-op= "x + y" | | | | |-exprs= | | | | | CallExpr ("tests/test1.js"@6.16-6.22:) | | | | | |-fn= | | | | | | Var ("tests/test1.js"@6.16-6.17:) | | | | | | |-id= f | | | | | |-args= | | | | | | OpExpr ("tests/test1.js"@6.18-6.21:) | | | | | | |-op= "x - y" | | | | | | |-exprs= | | | | | | | Var ("tests/test1.js"@6.18-6.19:) | | | | | | | |-id= x | | | | | | | Literal ("tests/test1.js"@6.20-6.21:) | | | | | | | |-value= 1 | | | | | CallExpr ("tests/test1.js"@6.25-6.31:) | | | | | |-fn= | | | | | | Var ("tests/test1.js"@6.25-6.26:) | | | | | | |-id= f | | | | | |-args= | | | | | | OpExpr ("tests/test1.js"@6.27-6.30:) | | | | | | |-op= "x - y" | | | | | | |-exprs= | | | | | | | Var ("tests/test1.js"@6.27-6.28:) | | | | | | | |-id= x | | | | | | | Literal ("tests/test1.js"@6.29-6.30:) | | | | | | | |-value= 2 Note that the parse tree construction is not fully implemented. Some more difficult things to parse (for loops, switch statements, with statement, object literals, regular expressions, consts, etc) are not yet done. Automatic semicolon insertion is also on the todo list. On the bright side, all the .js files of the parser (over 7,000 LOC) can be parsed by the parser. Also, the parser processes about 50,000 LOC per second, which should be OK for now (I haven't tried to optimize anything yet). Marc

1 0

New repos: tachyon and trace_analyser
by Erick Lavoie 24 Mai '10

24 Mai '10

following suggestion from Maxime, I created two empty repos, tachyon and trace_analyser to hold code from the js compiler and the trace analyser. See: http://docs.google.com/Doc?docid=0ARkLUElWcqxDZGdkOWo3c2ZfOTloamhkNm1ocw&hl… <http://docs.google.com/Doc?docid=0ARkLUElWcqxDZGdkOWo3c2ZfOTloamhkNm1ocw&hl…> For cloning them. Erick

2 1

SSA, ANF, CPS, IR
by Marc Feeley 17 Mai '10

17 Mai '10

The history of T article (http://www.paulgraham.com/thist.html) has some interesting things to say about intermediate representations, and SSA vs CPS in particular. Olin Shivers thinks that CPS representation is better than ANF (A-normal form). He also says that SSA is a rediscovery of CPS representation, under a different notation. I highly recommend you all read it. Marc

2 3

V8 Profiler
by Erick Lavoie 13 Mai '10

13 Mai '10

The V8 profiler can be used to profile both the C++ and Javascript code executing. http://code.google.com/p/v8/wiki/V8Profiler Ex: Produce a profiling trace: >./d8 --prof test.js Output looks like: function-creation,0x2f3200,0x61dca0 code-creation,LazyCompile,0x61e100,1428,"ProtocolPackage native d8.js:1150" code-creation,LazyCompile,0x61e760,202,"parse native json.js:61" function-creation,0x2e2a1c,0x61e760 code-creation,LazyCompile,0x61e880,142,"ParseJSONUnfiltered native json.js:30" function-creation,0x2e29e4,0x61e880 code-creation,Eval,0x61e960,108,"" Process the trace: >./tools/mac-tick-processor v8.log Output looks like: ticks parent name 27 20.5% v8::internal::CEntryStub::MajorKey 26 19.7% unibrow::Letter::Is 10 7.6% __mh_dylib_header 6 4.5% v8::internal::Scanner::ScanIdentifier 5 3.8% unibrow::Utf8::ReadBlock 1 20.0% Script: native string.js 3 2.3% v8::internal::Scanner::ScanJavaScript 3 2.3% ___keymgr_initializer Erick

3 2

Workshop on Self-sustaining Systems (S3) 2010
by Erick Lavoie 11 Mai '10

11 Mai '10

We might not have anything to publish by July 30th this year but it might be interesting to look forward for next year. Erick -------- Message original -------- Sujet: [fonc] CFP - S3 2010 Tokyo Date : Tue, 11 May 2010 10:48:12 -0700 De : Kim Rose <kim.rose(a)vpri.org> Répondre à : Fundamentals of New Computing <fonc(a)vpri.org> Pour : Fundamentals of New Computing <fonc(a)vpri.org> Please share this call with your University, colleagues, post to other lists, etc. Thank you! ------------------------------------------------------------------------------------------------------------------------------------------------------------ *** Workshop on Self-sustaining Systems (S3) 2010 *** September 27-28, 2010 The University of Tokyo, Japan http://www.hpi.uni-potsdam.de/swa/s3/s3-10/ In cooperation with ACM SIGPLAN === Call for papers === The Workshop on Self-sustaining Systems (S3) is a forum for discussion of topics relating to computer systems and languages that are able to bootstrap, implement, modify, and maintain themselves. One property of these systems is that their implementation is based on small but powerful abstractions; examples include (amongst others) Squeak/ Smalltalk, COLA, Klein/Self, PyPy/Python, Rubinius/Ruby, and Lisp. Such systems are the engines of their own replacement, giving researchers and developers great power to experiment with, and explore future directions from within, their own small language kernels. S3 will be take place September 27-28, 2010 at The University of Tokyo, Japan. It is an exciting opportunity for researchers and practitioners interested in self-sustaining systems to meet and share their knowledge, experience, and ideas for future research and development. --- Submissions and proceedings --- S3 invites submissions of high-quality papers reporting original research, or describing innovative contributions to, or experience with, self-sustaining systems, their implementation, and their application. Papers that depart significantly from established ideas and practices are particularly welcome. Submissions must not have been published previously and must not be under review for any another refereed event or publication. The program committee will evaluate each contributed paper based on its relevance, significance, clarity, and originality. Revised papers will be published as post-proceedings in the ACM Digital Library. Papers should be submitted electronically via EasyChair at http://www.easychair.org/conferences/?conf=s32010 in PDF format. Submissions must be written in English (the official language of the workshop) and must not exceed 10 pages. They should use the ACM SIGPLAN 10 point format, templates for which are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. --- Venue --- The University of Tokyo, Komaba Campus, Japan (getting here...) --- Important dates --- Submission of papers: July 30, 2010 Author notification: August 27, 2010 Early registration: September 3, 2010 Revised papers: September 10, 2010 S3 workshop: September 27-28, 2010 Final papers for ACM-DL post-proceedings: October 15, 2010 --- Chairs --- Robert Hirschfeld (Hasso-Plattner-Institut Potsdam, Germany) hirschfeld(a)hpi.uni-potsdam.de Hidehiko Masuhara (The University of Tokyo, Japan) masuhara(a)graco.c.u-tokyo.ac.jp Kim Rose (Viewpoints Research Institute, USA) kim.rose(a)vpri.org --- Program committee --- Carl Friedrich Bolz, University of Duesseldorf, Germany Johan Brichau, Universite Catholique de Louvain, Belgium Shigeru Chiba, Tokyo Institute of Technology, Japan Brian Demsky, University of California, Irvine, USA Marcus Denker, INRIA Lille, France Richard P. Gabriel, IBM Research, USA Michael Haupt, Hasso-Plattner-Institut, Germany Robert Hirschfeld, Hasso-Plattner-Institut, Germany (co-chair) Atsushi Igarashi, University of Kyoto, Japan David Lorenz, The Open University, Israel Hidehiko Masuhara, University of Tokyo, Japan (co-chair) Eliot Miranda, Teleplace, USA Ian Piumarta, Viewpoints Research Institute, USA Martin Rinard, MIT, USA Antero Taivalsaari, Nokia, Finland David Ungar, IBM, USA _______________________________________________ fonc mailing list fonc(a)vpri.org http://vpri.org/mailman/listinfo/fonc

1 0

Re: [Tachyon-list] Using V8 Developer Shell (D8)
by Erick Lavoie 11 Mai '10

11 Mai '10

Le 10-05-05 16:30 , chevalma(a)iro.umontreal.ca a écrit : > Pretty cool. Does it require the C++ functions to take V8 implementation > specific objects as arguments (eg: some JSObject class), or do we declare > the types that the C++ functions take? > They use an Arguments wrapper object. I'll dig further into this. > Just wondering if we will be able to use the same C++ code directly in V8 > and in our own implementation. > > - Maxime > Erick > >> I just found that the option to call native functions can simply be >> passed as an argument to the d8 executable. >> >> Ex: >> >> ./d8 --allow_natives_syntax >> d8> var f = %CompileString("var x = 2;",false); >> d8> f >> function var x = 2; >> d8> f() >> d8>x >> 2 >> >> For other options, simply type: >> >> ./d8 --help >> >> >> As a side note, to read a file as a string from the d8 prompt, simply do: >> >> var s = read("my_test_file.js"); >> >> Erick >> >> >> >> >> Le 10-05-05 14:49 , Erick Lavoie a écrit : >> >>> V8 provides a nice developer shell to interactively execute and debug >>> javascript code using their Engine. >>> >>> The build instructions as well as the dependencies can be found here >>> <http://code.google.com/apis/v8/build.html>. >>> >>> To allow calling native C++ functions from javascript directly such as >>> what is done in the standard libraries (see src/v8natives.js), simply >>> set the "allow_natives_syntax" flag from src/flag-definitions.h to >>> "true". This will allow calling functions like %CompileString directly. >>> >>> To see how C++ functions can be exposed to javascript, look at void >>> Shell::Initialize() from src/d8.cc. >>> >>> When an error occurs, the d8 shell automatically enters debug mode. >>> The listing of available commands can be found at "function >>> DebugRequest" of src/d8.js. >>> >>> Erick >>> >> _______________________________________________ >> Tachyon-list mailing list >> Tachyon-list(a)iro.umontreal.ca >> https://webmail.iro.umontreal.ca/mailman/listinfo/tachyon-list >> >> > >

5 12

PLDI Registration
by Maxime Chevalier-Boisvert 10 Mai '10

10 Mai '10

The PLDI early registration will be closing in a few hours. Are we going? - Maxime

1 0

V8 Embedder's Guide
by Erick Lavoie 10 Mai '10

10 Mai '10

Really good explanations of the concepts behind the implementation of V8: http://code.google.com/apis/v8/embed.html

1 0

Doxygen reference for v8
by Erick Lavoie 06 Mai '10

06 Mai '10

http://izs.me/v8-docs/ For an example usage of the Arguments class to add our own C++ functions, see: http://izs.me/v8-docs/shell.cc-example.html All the important class references are one click away, which is pretty neat! Erick

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Tachyon-list Mai 2010