Open
Bug 1284975
Opened 8 years ago
Updated 3 months ago
[meta] Make SpiderMonkey clean on UBSan
Categories
(Core :: JavaScript Engine, defect, P2)
Core
JavaScript Engine
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: terrence, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: meta)
Attachments
(1 file)
9.50 KB,
text/plain
|
Details |
We have a number of open bugs (e.g. 1281168, 1262015, and everything [gcc 6.1]) that reek of "miscompilation". Fixing all of our UBSan reports seems like it might be a faster way to fix these than hunting down each such miscompilation one at a time.
Luckily, running jsapi-tests under UBSan turned up a number of scary, but correct and actionable, reports that we should fix. I'll file bugs blocking this one with patches. Help would of course be appreciated, if anyone has spare cycles. It's really easy to get UBSan running and it's reports are generally pretty obviously correct and relatively easy to address; ping me on IRC if you need help.
Comment 1•8 years ago
|
||
This is a most noble goal to attain.
Updated•8 years ago
|
Assignee: nobody → terrence
Comment 2•7 years ago
|
||
List of UBSan errors when running jstests+jit-tests with default options. Already excluding the issues fixed in bug 1401145, bug 1401191, bug 1401200, bug 1401209, and bug 1401515.
Updated•7 years ago
|
Assignee: terrence.d.cole → nobody
Priority: -- → P2
Comment 3•6 years ago
|
||
Could we build with `-f[wt]rapv -fno-strict-aliasing -fno-delete-null-pointer-checks` and insert a compiler plugin that modifies the IR to not require pointer alignment?
Comment 4•3 years ago
|
||
All depending bugs are now fixed.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•