Closed
Bug 1464751
Opened 7 years ago
Closed 7 years ago
If there is no JIT, there should be no JIT signal handlers
Categories
(Core :: JavaScript Engine: JIT, enhancement, P5)
Tracking
()
RESOLVED
FIXED
mozilla62
People
(Reporter: spectre, Assigned: spectre)
Details
Attachments
(1 file, 2 obsolete files)
1.19 KB,
patch
|
spectre
:
review+
RyanVM
:
approval-mozilla-esr60+
RyanVM
:
checkin+
|
Details | Diff | Splinter Review |
On platforms where JS_CODEGEN_NONE is in effect, such as the ppc64le Talos II I'm typing this on, the browser immediately asserts if any signal occurs (usually shortly after startup) in js/src/wasm/WasmSignalHandlers.cpp. So, we shouldn't be trying to install signal handlers on those platforms.
Assignee | ||
Comment 1•7 years ago
|
||
Pretty self-explanatory.
Lars, please advise if you are not an appropriate reviewer.
Comment 2•7 years ago
|
||
I guess the patch is probably fine but what branch is this for? It doesn't seem related to current mozilla-central.
Updated•7 years ago
|
Priority: -- → P5
Assignee | ||
Comment 3•7 years ago
|
||
Sorry, that was against mozilla-release. Regenerating against mozilla-central. Apologies.
Assignee | ||
Comment 4•7 years ago
|
||
Rebased to tip.
Attachment #8981059 -
Attachment is obsolete: true
Attachment #8981059 -
Flags: review?(lhansen)
Attachment #8981217 -
Flags: review?(lhansen)
Comment 5•7 years ago
|
||
Comment on attachment 8981217 [details] [diff] [review]
Don't install wasm signal handlers on platforms without a JIT
Review of attachment 8981217 [details] [diff] [review]:
-----------------------------------------------------------------
::: js/src/wasm/WasmSignalHandlers.cpp
@@ +1393,5 @@
> return sHaveSignalHandlers;
> sTriedInstallSignalHandlers = true;
>
> +#if defined (JS_CODEGEN_NONE)
> + // If there is no JIT, then there should be no signal handlers.
If it were me I would write "no Wasm signal handlers", since that's what we're trying to install here.
Attachment #8981217 -
Flags: review?(lhansen) → review+
Assignee | ||
Comment 6•7 years ago
|
||
Comment changed as requested, carrying forward r+, check-in requested. Thanks!
Attachment #8981217 -
Attachment is obsolete: true
Attachment #8981240 -
Flags: review+
Attachment #8981240 -
Flags: checkin?
Updated•7 years ago
|
Keywords: checkin-needed
Pushed by apavel@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f9e9764dc517
Don't install wasm signal handlers on platforms without a JIT. r=lth
Keywords: checkin-needed
Comment 8•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
Updated•7 years ago
|
Attachment #8981240 -
Flags: checkin? → checkin+
Comment 9•6 years ago
|
||
Comment on attachment 8981240 [details] [diff] [review]
Don't install wasm signal handlers on platforms without a JIT v2
[Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration:
User impact if declined: crash at start on platforms with no JITs. So it'd be nice for tier 3 platforms. Somebody asked for this on irc, and I figured I'd ask, if this can ride along another ESR build.
Fix Landed on Version: 62
Risk to taking this patch (and alternatives if risky): very very very very low
String or UUID changes made by this patch: n/a
Attachment #8981240 -
Flags: approval-mozilla-esr60?
Comment 10•6 years ago
|
||
Comment on attachment 8981240 [details] [diff] [review]
Don't install wasm signal handlers on platforms without a JIT v2
Fixes a startup crash for Tier 3 platforms without a JIT. Approved for ESR 60.3.
Attachment #8981240 -
Flags: approval-mozilla-esr60? → approval-mozilla-esr60+
Comment 11•6 years ago
|
||
bugherder uplift |
status-firefox-esr60:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•