[Webkit-unassigned] [Bug 251722] New: [ BigSur+ Debug JSC ](New Tesrts?): ASSERTION FAILED: mode == ManualOperandSpeculation || edge.useKind() == HeapBigIntUse

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 3 14:42:05 PST 2023


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

            Bug ID: 251722
           Summary: [ BigSur+ Debug JSC ](New Tesrts?): ASSERTION FAILED:
                    mode == ManualOperandSpeculation || edge.useKind() ==
                    HeapBigIntUse
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: Jenner at apple.com

wasm.yaml/wasm/stress/js-to-wasm-i64-register.js.wasm-eager
wasm.yaml/wasm/stress/js-to-wasm-i64-stack.js.wasm-eager
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.default-wasm
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-air
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-b3
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-bbqb3
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-eager
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-eager-jettison
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-no-cjit
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-simd
wasm.yaml/wasm/stress/js-to-wasm-many-i64.js.wasm-slow-memory


Appear to be hitting the following assertion BigSur and Monterey Debug:

ASSERTION FAILED: mode == ManualOperandSpeculation || edge.useKind() == HeapBigIntUse

HISTORY:
https://results.webkit.org/?suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&suite=javascriptcore-tests&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.wasm-eager-jettison&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.wasm-no-cjit&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.wasm-simd&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.wasm-slow-memory&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.default-wasm&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.wasm-air&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-many-i64.js.wasm-b3&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-i64-register.js.wasm-eager&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-i64-register.js.wasm-eager-jettison&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-i64-stack.js.wasm-eager&test=wasm.yaml%2Fwasm%2Fstress%2Fjs-to-wasm-i64-stack.js.wasm-eager-jettison


They appear to all have been newly added tests at https://commits.webkit.org/259584@main

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230203/5a7c495e/attachment.htm>


More information about the webkit-unassigned mailing list