Open
Bug 1169271
Opened 10 years ago
Updated 3 years ago
Improve code coverage for AtomicsObject.cpp
Categories
(Core :: JavaScript Engine, defect, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: lth, Unassigned)
References
(Blocks 1 open bug)
Details
This shows the current coverage:
https://www.tjhsst.edu/~jcranmer/m-ccov/js/src/builtin/AtomicsObject.cpp.html
Coverage is quite low, mainly because:
- some of the atomics callouts for asm.js is not tested, because they are
only needed for ARMv6
- the futex code is not tested by the current test suite
Additionally:
- error branches (wrong array type, out of bounds) are not exercised
Landing bug 1135026 will help with the futex coverage. It should also be easy to test the error branches.
The asm.js callouts for ARMv6 can probably only be exercised on other platforms by changing some conditions for their enabling; will need investigating.
| Reporter | ||
Comment 1•10 years ago
|
||
On a related note, in MCallOptimize.cpp there is a lack of coverage for double-precision arguments, and for the wrong number of arguments, when inlining atomics:
https://www.tjhsst.edu/~jcranmer/m-ccov/js/src/jit/MCallOptimize.cpp.html
| Reporter | ||
Comment 2•10 years ago
|
||
In CodeGenerator.cpp (search for "atomic") there are some untaken paths, one in CMPXCHG but more notably there appear to be no test cases that trigger the use of LAtomicTypedArrayElementBinopForEffect.
https://www.tjhsst.edu/~jcranmer/m-ccov/js/src/jit/CodeGenerator.cpp.html
| Reporter | ||
Comment 3•10 years ago
|
||
No test case touches the useRegisterAtStart case in LIRGeneratorX86::visitAsmJSAtomicBinopHeap in https://www.tjhsst.edu/~jcranmer/m-ccov/js/src/jit/x86/Lowering-x86.cpp.html.
| Reporter | ||
Comment 4•10 years ago
|
||
Several lacunae in LIRGeneratorX86Shared::lowerAtomicTypedArrayElementBinop in https://www.tjhsst.edu/~jcranmer/m-ccov/js/src/jit/x86-shared/Lowering-x86-shared.cpp.html, one having to do with uint32 I think and another having to do with operations for effect.
| Reporter | ||
Updated•8 years ago
|
Priority: -- → P3
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•