[Webkit-unassigned] [Bug 129155] [Win][LLINT] Many JSC stress test failures.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=129155





--- Comment #8 from Mark Lam <mark.lam at apple.com>  2014-02-21 12:13:24 PST ---
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #5)
> > > Results for JSC stress tests:
> > >     18 failures found.
> > > 
> > > So there seems to be some regressions when using the x86 backend compared to the C Loop backend, I will look into those next.
> > 
> > Beware of https://bugs.webkit.org/show_bug.cgi?id=129099 which may contribute some failures.  Note: some stress tests will turn on the DFG even if you don’t have it on by default.  The only way it doesn’t get turned on is if the DFG is not built in.  The C loop LLINT build benefits from that.
> 
> Ok, so maybe I should run a test with DFG and LLINT enabled?

Just to clarify: the LLINT is always enabled.  It’s either the C loop LLINT or the ASM LLINT.

The DFG can be disabled at runtime, but some jsc stress tests will turn it back on because that is the purpose of those tests i.e. to test the DFG.  If you run them with the DFG not built in the binary (like the C loop build), then the DFG won’t come into play.

To remove the effects of the DFG, don’t build the DFG into the code.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.