On 2/12/2014 2:58 PM, Ryan VanderMeulen wrote:
Note that it's not really XP per se, it's Windows Server 2003, which
is what our build slaves are.
I don't know about the Jit runs on Try as they're currently perma-fail
for other reasons.
-Ryan
I pinged philor about it and he says that we are
As hinted at previously, the DevTools group would like to introduce a
new representation of saved (not live) JS stacks to SpiderMonkey. Our
immediate need is to record the stacks at which JS objects are
allocated, for our memory profiling tools, but we'd like to introduce
something general
That's great to hear. Thanks for working on this!
On Wed, Feb 12, 2014 at 3:25 PM, Jim Blandy jbla...@mozilla.com wrote:
As hinted at previously, the DevTools group would like to introduce a new
representation of saved (not live) JS stacks to SpiderMonkey. Our immediate
need is to record the
Some may believe it is time for SpiderMonkey standalone builds for
Windows to return, as personally I am admittedly increasingly frustrated
at the increasing numbers of Windows-specific build failures. (More may
come as :glandium points out, as long as Windows standalone builds are
not on
I think folks are being a little optimistic about the impact of having
MIPS code in tree. My experience has been that it usually does end up
being a distraction.
If we truly treat MIPS as a tier-3 platform - for example, if we don't
hesitate to remove, refactor, or even just fiddle with the
5 matches
Mail list logo
