[webkit-dev] arm jit
ggaren at apple.com
Tue Jun 9 15:03:31 PDT 2009
> Today, we realized that there is a new ARM JIT port for WebKit. (http://trac.webkit.org/changeset/44514
> ) Congratulations on getting this working!, great job.
> I cannot conceal how disappointed I am, as is the whole team at
I'm sorry to hear that. I understand your disappointment, but I have
to admit that I'm excited to have a close-to-enabled, fast ARM JIT in
infrastructure and design.
> It was months ago, when we presented you our first results in the
> Bugzilla (https://bugs.webkit.org/show_bug.cgi?id=24986). Since
> then, we exchanged ideas in several comments and even received
> feedbacks and suggestions from you. Now, I pose the question
> (possibly only to myself): "For what end?" I'm quite sure that the
> work on your side has been ongoing for some time now. Still, you did
> not mention anything. We did not even get a notification on the new
> Of course, we've felt that you were reluctant to accept our
> implementation. At least, now we know why.
> As WebKit currently is, it is not an open community. Not at all.
I don't think that's fair.
Looking at https://bugs.webkit.org/show_bug.cgi?id=24986, I see three
detailed comments by Oliver Hunt, and two by Gavin Barraclough,
explaining our thinking about how an ARM JIT should be organized to
best effect. I think you'll find those comments strongly reflected in http://trac.webkit.org/changeset/44514
> Let me ask two final questions:
> - Are you still looking for patches, bug reports, feature requests,
> - Should we ask for credits in the new files, as it was done by you
> when we first published our JIT implementation? I'm quite sure that
> we can state the same argument: "a number of the new files appear to
> have taken large chunks of logic from existing jit files".
Generally, a new file that copies substantial code from an old file
should include the old file's copyrights, along with the new author's
copyright. Usually, this happens naturally via svn cp, but sometimes
people forget or use other processes. If you notice a patch that is
remiss in this area, please do mention something, with specifics.
More information about the webkit-dev