Closed
Bug 582693
Opened 14 years ago
Closed 14 years ago
Trace JIT inactive for optimized OS X ppc emulation
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: sfink, Unassigned)
Details
This may be a known and irrelevant limitation for all I know, but in tracking down a test failure (bug 582172) with my patch for bug 507012, I discovered that TraceMonkey doesn't seem to be able to JIT simple code when running in ppc emulation mode on an i386 -- but only for an optimized build, which is why I'm filing a bug. Is this a known limitation? I've been having trouble generating my own builds to test this further. I really don't understand why. I seem to having a workaround; see bug 582690.
Comment 1•14 years ago
|
||
We never supported PPC with the trace JIT. I don't think there are plans to support PPC in Jaegermonkey either. I am happy to guide volunteers make the tracer work. A backend already exists and just needs a little fixing.
Comment 2•14 years ago
|
||
There are no plans to support PPC in Jaegermonkey as we do not ship for PPC. However, we would definitely accept a PPC port. It would require adding PPC support to the assembler we share with WebKit, which should not be much work.
Reporter | ||
Comment 3•14 years ago
|
||
I'm not the person to do a PPC port; I only ran into it because I was foolish enough to add a test case to check whether simple code is JITted. I'd rather not eliminate that test completely; it seems useful for catching regressions. What is an appropriate way to check whether JIT is expected to work from a jsapi-tests/ test? (I'm only handling TM for now, but would be happy to know the answers for both TM and JM.)
Reporter | ||
Comment 4•14 years ago
|
||
Ah. It looks like TRACING_ENABLED(cx) (aka cx->jitEnabled) should be good enough. I'll mark this bug as WONTFIX, unless someone would rather reuse it for a feature request.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Reporter | ||
Comment 5•14 years ago
|
||
(but see bug 582778)
You need to log in
before you can comment on or make changes to this bug.
Description
•