Hi Matt
Welcome to the project Matt it is great to have people working on V8.

With regard to getting started then two the issues you have located could be
good starting points. I suggest starting with issue 213 which is basically
adding binary search. Parts of the code involved (locating line ends) have
moved from JavaScript to C++ so you might look at whether to put the binary
search in C++ or JavaScript. I suggest creating a test case which is badly
hurt by the current implementation. Regarding issue 96 this might be a
rather simple timing issue which is not handled consistently by the test,
but I am not sure. Issue 212 will be rather complicated, and might also
be influenced by some other work on the compiler so I suggest postponing
this.

Regards,
Søren

On Wed, Feb 25, 2009 at 6:49 PM, Matt H <[email protected]> wrote:

>
> I'm here to introduce myself and hopefully get involved as an external
> contributor to V8 in a part-time manner (10-15 hours/week)
>
> About 10 years ago, I worked on the DEC Alpha C & C++ compiler for a
> couple of years (both UNIX and VMS).  I started out doing compiler
> intrinsics in the C compiler and migrated to owning the debugger
> integration in C++, namely implementing the new debug symbol
> generation algorithm in the (then) new C++ version 6.  I've been out
> of the compiler loop for a few years but would like to get back.
>
> Is there anything specific that anybody would like me to start with?
> While poking around the issues list, things that looked interesting
> were #96 (ThreadedDebugging flakey), 212 (mutating local variables)
> and 213 (locating source code lines) -- all of which happen to be
> logged by Søren.  These are ones that caught my eye and by no means
> are ones I'm going to argue I should take.  I'd rather be useful to
> the project than selfish in what I work on.
>
> Thanks much
>
> - Matt
> >
>

--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to