Re: [webkit-dev] interested in js speed-up

2008-03-23 Thread ToolmakerSteve
Akos Kiss-2 wrote: Oh, you must be surely right. Let's stop all alternative development works. The new motto is: One size fits all. BR, -Akos PS: Sorry, I could not refrain from responding. No worries. If you read through the end of the thread to see what I already posted later

Re: [webkit-dev] interested in js speed-up

2008-03-18 Thread Akos Kiss
Dear Geoff, let me ask one more question: when is this bytecode approach expected to get into the mainline of WebKit? Cheers, Akos Geoffrey Garen írta: Hi Akos. Hi Geoff, thanks for the info. It seems to me that your answers cancelled my options. :) Optimizing the AST is not the best

Re: [webkit-dev] interested in js speed-up

2008-03-13 Thread Akos Kiss
Oh, you must be surely right. Let's stop all alternative development works. The new motto is: One size fits all. BR, -Akos PS: Sorry, I could not refrain from responding. ToolmakerSteve írta: Akos Kiss-2 wrote: we got interested in speeding up the JavaScript engine of WebKit. But, But,

Re: [webkit-dev] interested in js speed-up

2008-03-13 Thread Maciej Stachowiak
On Mar 12, 2008, at 4:57 PM, ToolmakerSteve wrote: Akos Kiss-2 wrote: we got interested in speeding up the JavaScript engine of WebKit. But, But, the world is moving on to ECMAScript 4 / Javascript 2. Does it make sense to do anything other than to use, and to help improve, the open

Re: [webkit-dev] interested in js speed-up

2008-03-12 Thread Akos Kiss
Hi Geoff, thanks for the info. It seems to me that your answers cancelled my options. :) Optimizing the AST is not the best way to go since execution moves to bytecode. And designing a new bytecode is not an option anymore since you are already doing it. :) However, this opens new

Re: [webkit-dev] interested in js speed-up

2008-03-12 Thread Geoffrey Garen
Hi Akos. Hi Geoff, thanks for the info. It seems to me that your answers cancelled my options. :) Optimizing the AST is not the best way to go since execution moves to bytecode. And designing a new bytecode is not an option anymore since you are already doing it. :) Sorry to spoil

Re: [webkit-dev] interested in js speed-up

2008-03-12 Thread ToolmakerSteve
Akos Kiss-2 wrote: we got interested in speeding up the JavaScript engine of WebKit. But, But, the world is moving on to ECMAScript 4 / Javascript 2. Does it make sense to do anything other than to use, and to help improve, the open source Mozilla/Tamarin codebase? That will give you the

[webkit-dev] interested in js speed-up

2008-03-04 Thread Akos Kiss
Dear all, (sorry, I don't know whom to contact directly) we have a small team at the Department of Software Engineering, University of Szeged, Hungary, and we got interested in speeding up the JavaScript engine of WebKit. We would be happy to use our compiler background for the benefit of the

Re: [webkit-dev] interested in js speed-up

2008-03-04 Thread Geoffrey Garen
Hi Akos. Any help speeding up JavaScriptCore is welcome. The current plan is: 1. Convert from an AST execution engine to a custom bytecode engine 2. Perform low-cost optimizations on the custom bytecode (e.g., simple type inference, peephole optimization, constant folding, copy propagation,

Re: [webkit-dev] interested in js speed-up

2008-03-04 Thread Edward Rowe
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey Garen Sent: Tuesday, March 04, 2008 12:01 PM To: Akos Kiss Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] interested in js speed-up Hi Akos. Any help speeding up JavaScriptCore is welcome. The current plan is: 1. Convert from an AST