\o/ Agreed! \o/
-Gary
On 7/29/13 5:24 PM, Luke Wagner wrote:
JS engine hackers,
for the last five years, we've had an exciting sequence of jit compilers added,
redesigned and removed. With the recent completion of the IonMonkey and
Baseline projects, I think we're finally in a position
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
On 2/13/14, 12:18 PM, Steve Fink wrote:
Sounds like the sticking point is finding someone who will agree to
keep them alive. There's no point in turning them on if they're going
to be broken for weeks/months at a stretch.
This can be mitigated as per Valgrind by having per-commit builds as
How useful would it be for the compilation process to produce a binary
as well as a symbols file for everyone?
My usecase would be to be able to archive just the binary and symbols in
a cache folder so I don't need to compile it again when testing testcases.
Currently if I just keep the
On 4/11/14, 2:37 AM, Nicolas B. Pierron wrote:
Thanks for doing this priority list, at least this make things clear. :)
I would suggest to amend it as follow:
6a. *reproducible* topcrash bugs
6b. fuzzblockers
[…]
9f. *non-reproducible* topcrash bugs
- top-crash are not always
5 matches
Mail list logo
