GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing github.com — The JIT's "pure" `_BINARY_OP` evaluation produces UB (and incorrect results) · Issue #136183 · python/cpython Closed Labels 3.15bugs and security fixesbugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-JITtype-crashA hard crash of the interpreter, possibly with a core dumpA hard crash of the interpreter, possibly with a core dump DescriptionCrash reportThis code snippet crashes when the JIT is enabled: for _ in range(4096): 2 ** 65 I believe this is caused by GH-132733. Specifically, the abstract interpreter generator "thinks" that the operation itself can escape, and spills cpython/Python/optimizer_cases.c.h Line 2726 in 93809a9
It also never writes the actual result to the stack once it has been computed, leaving the garbage value in its place. The fix is probably to teach the code generator that nothing using this "pure" constant evaluation mechanism can escape. Linked PRsActivity
MetadataMetadataAssigneesLabels3.15bugs and security fixesbugs and security fixesinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)topic-JITtype-crashA hard crash of the interpreter, possibly with a core dumpA hard crash of the interpreter, possibly with a core dump ProjectsMilestoneRelationshipsDevelopmentIssue actions | ||
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |