Proxy performance: JIT-compilation?

[Alex Vincent]

So, how many boxes of chocolates do I need to send to the two big vendors
in Mountain View?  :-)

It's been fifteen years since I seriously tried to profile C++ code, and I
didn't really know what I was doing back then:  unfamiliar tools, and less
competence in C++ than I would've liked.  What little knowledge of
profiling I had back then has long since faded.

Even if I could generate a pretty picture of how long we spent in each code
path, I wouldn't know how to interpret it.

I recently submitted a patch for improving error reporting in SpiderMonkey
[1], so I can occasionally dip my toes in the JSAPI code...

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1383630

On Fri, Aug 4, 2017 at 2:52 PM, Allen Wirfs-Brock <allen at wirfs-brock.com>
wrote:

> I don’t think the barriers to such optimization are technical.  It’s more
> a matter of convincing that engine implementors that doing the work
> (probably significant)  to optimizing Proxies in this manner is a sound
> investment and hight priority
>

-- 
"The first step in confirming there is a bug in someone else's work is
confirming there are no bugs in your own."
-- Alexander J. Vincent, June 30, 2001
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20170804/46a5a89e/attachment.html>