The prover reasons about a FLOAT as a number: Y == Y holds, and X < Z or X >= Z. The interpreter let 1.0E308 * 10.0 become infinity and X - X become NaN and carried on, so a run broke claims the prover had proved (tests/prover/float-overflow.pseudo proved ASSERT Y == Y with Y NaN). The notation already stops on a FLOAT division by zero and on a whole number past 2^53 - 1. It now also stops, with an 'overflow' error, when an arithmetic result, a built-in's result or a literal is not a finite number (finiteCheck in interp.js). Every run then stays inside what a proof covers. Regression programs whose fix was to the language rather than to a rule now say where the run must stop, with a RUN-STOPS header the soundness test checks. A unit that does FLOAT arithmetic now carries a 'float-model' note: FLOAT is treated as a finite number, rounding is opaque, and the lab stops past about 1.8e308, while the generated Mojo goes on with inf or nan (stated for a division by zero, the case probes/float-special has verified). New probe mojo/probes/float-overflow.mojo asks the compiler what a Float64 product past the largest double gives; it is unverified and needs pixi run mojo-verify-item 'probes/float-overflow' (network). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FgvbRdoEheAHqsRmr2WuKZ
12 KiB
12 KiB
Corpus status against mojo_1_1_0 (Mojo 1.1.0)
Generated by python3 scripts/mojo/corpus.py status from the goldens in this directory. Do not edit.
| corpus | pass | fail | observed | skipped | unverified |
|---|---|---|---|---|---|
| diagnostics | 0 | 0 | 0 | 42 | 132 |
| local | 18 | 0 | 0 | 0 | 0 |
| manual | 144 | 55 | 0 | 1 | 0 |
| probes | 13 | 0 | 71 | 0 | 1 |
| quest | 170 | 0 | 0 | 0 | 0 |
| stress | 40 | 0 | 0 | 0 | 0 |
Failures
manual/code/manual/basics/python_integration: exited abnormally (exit code 132)manual/code/manual/control-flow/for_loop: exited abnormally (exit code 132)manual/code/manual/errors/conditional_context_mgr: exited abnormally (exit code 1)manual/code/manual/errors/stacktrace_error: exited abnormally (exit code 1)manual/code/manual/errors/test_conditional_context_mgr: did not compilemanual/code/manual/errors/test_context_mgr: did not compilemanual/code/manual/errors/test_enumerated_errors: did not compilemanual/code/manual/errors/test_error_interaction: did not compilemanual/code/manual/errors/test_handle_error: did not compilemanual/code/manual/errors/test_never_type: did not compilemanual/code/manual/errors/test_parametric_raises: did not compilemanual/code/manual/errors/test_typed_errors_doc: did not compilemanual/code/manual/errors/test_typed_errors_edge_cases: did not compilemanual/code/manual/errors/test_typed_errors_testing: did not compilemanual/code/manual/errors/test_variant_errors: did not compilemanual/code/manual/lifecycle/explicit-destroy/tests: exited abnormally (exit code 1)manual/code/manual/metaprogramming/materialization/comptime_subexpression: did not compilemanual/code/manual/pointers/using-pointers/python_pointer: exited abnormally (exit code 132)manual/code/manual/python/types/mojo_types: exited abnormally (exit code 132)manual/code/manual/python/types/python_compare: exited abnormally (exit code 132)manual/code/manual/python/types/python_conversions: exited abnormally (exit code 132)manual/code/manual/python/types/python_dict: exited abnormally (exit code 132)manual/code/manual/python/types/python_list: exited abnormally (exit code 132)manual/code/manual/python/types/python_tuple: exited abnormally (exit code 132)manual/code/manual/quickstart/quickstart: exited abnormally (exit code 132)manual/code/tools/notebooks/gpu_hello: did not compilemanual/code/tools/notebooks/hello_writing: did not compilemanual/code/tools/notebooks/vector_addition: did not compilemanual/snippet/manual-control-flow-24: exited abnormally (exit code 132)manual/snippet/manual-control-flow-25: exited abnormally (exit code 132)manual/snippet/manual-control-flow-26: exited abnormally (exit code 132)manual/snippet/manual-errors-1: did not compilemanual/snippet/manual-errors-5: did not compilemanual/snippet/manual-errors-6: did not compilemanual/snippet/manual-errors-7: did not compilemanual/snippet/manual-errors-8: did not compilemanual/snippet/manual-parameters-index-1: did not compilemanual/snippet/manual-parameters-index-2: did not compilemanual/snippet/manual-parameters-index-4: did not compilemanual/snippet/manual-parameters-index-7: did not compilemanual/snippet/manual-pointers-using-pointers-4: did not compilemanual/snippet/manual-python-types-1: exited abnormally (exit code 132)manual/snippet/manual-python-types-2: exited abnormally (exit code 132)manual/snippet/manual-python-types-3: exited abnormally (exit code 132)manual/snippet/manual-python-types-4: exited abnormally (exit code 132)manual/snippet/manual-python-types-5: exited abnormally (exit code 132)manual/snippet/manual-python-types-6: did not compilemanual/snippet/manual-types-7: did not compilemanual/snippet/manual-values-lifetimes-2: did not compilemanual/snippet/manual-values-lifetimes-3: did not compilemanual/snippet/manual-values-ownership-1: did not compilemanual/snippet/manual-values-ownership-2: did not compilemanual/snippet/manual-values-ownership-3: did not compilemanual/snippet/manual-values-ownership-4: did not compilemanual/snippet/manual-values-ownership-5: did not compile
Probes
| probe | question | verdict |
|---|---|---|
check-aliasing |
the compiler's words for passing one value as mut and as a second argument | pass |
check-implicit-copy |
the compiler's words for copying a type that is not ImplicitlyCopyable | pass |
check-implicit-declaration |
1.1.0 notes: assigning an undeclared name is an error | pass |
check-missing-raises |
calling a raising function from a non-raising one | pass |
check-uninitialized |
the compiler's words for reading a variable before it is set | pass |
check-use-after-move-on-one-path |
moved out on one path, read after the branch: the compiler's words | pass |
check-use-after-move |
the compiler's words for using a value after ^ moved it | pass |
comptime-if-for |
comptime for and comptime if in a function body | observed |
dialect-del |
1.0.0 notes said del still works, deprecated; does it in 1.1.0? | observed |
dialect-fn |
1.1.0 notes: fn is removed | pass |
dialect-read |
1.1.0 notes: the read convention is a hard error | pass |
dialect-register-passable |
deprecated in 0.26.2: is @register_passable("trivial") an error or a warning in 1.1.0? | observed |
dialect-value |
is the @value decorator still accepted? | observed |
dict-missing-key |
what does reading a missing Dict key raise, and how is it printed? | observed |
dict-order |
does a Dict iterate in insertion order, and after a pop and re-insert? | observed |
error-assert-statement |
is there an assert statement, and what does a failing one do? | observed |
error-debug-assert |
is debug_assert checked by default on godbolt's build? | observed |
error-exit-code |
does std.sys.exit set the exit code after output? | observed |
error-try-finally |
the order of try, except and finally | observed |
error-unhandled |
what reaches stdout, stderr, and the exit code when main raises? | observed |
float-mixed |
can an Int and a Float64 be combined without a conversion? | observed |
float-overflow |
does a Float64 product past the largest double give inf at run time, and inf - inf nan? | unverified |
float-print |
how does print format Float64 values? | observed |
float-round |
what does round() do on halves? | observed |
float-special |
how are inf, -inf and nan printed after a run-time division by zero? | observed |
float-to-int |
does Int(x) truncate toward zero? | observed |
float32-print |
how does print format Float32 values? | observed |
godbolt-asm-and-run |
does one request return both the listing and the program's output? | observed |
godbolt-asm |
the listing for a small function: labels, and source line numbers on instructions | observed |
godbolt-compile-button |
the Compile button's request: -O0, line tables, listing and output in one answer | pass |
godbolt-line-tables-O0 |
with -O0 and line tables, are source lines attached, and is the function list unchanged? | observed |
godbolt-line-tables |
with --debug-level=line-tables, does godbolt attach source lines to instructions (optimised build)? | observed |
godbolt-opt-O0 |
is -O0 accepted, and how does the listing change? | observed |
godbolt-stdin |
does the Compile button's request (compile and run in one) deliver stdin? (run mode did not: input-lines) | pass |
input-eof |
what does input() do at the end of input? | observed |
input-lines |
input() reads one line per call; atol parses an Int | observed |
input-parse-error |
what does atol raise on text that is not a number? | observed |
int-div-zero |
what happens on integer division by zero at run time (output, exit code)? | observed |
int-floordiv |
does // floor toward negative infinity on Int? | observed |
int-literal-too-big |
is a literal too big for Int a compile error? | observed |
int-mod |
what sign does % give with negative operands? | observed |
int-overflow-int |
what is Int.MAX, and what is Int.MAX + 1 at run time? | observed |
int-overflow-int8 |
does Int8 wrap on overflow at run time? | observed |
int-pow-shift |
what do ** and shifts give on Int at run time? | observed |
int-truediv |
what does / do on two Int values, positive and negative? | observed |
int-uint-wrap |
does UInt8 wrap below zero? | observed |
lib-parallelize |
is parallelize importable from std.algorithm in 1.1.0? | observed |
lib-vectorize |
is vectorize importable from std.algorithm in 1.1.0? | observed |
life-asap-expression |
the manual's ASAP example: which values are destroyed, in what order, inside one expression? | observed |
life-borrow-lifetime |
Stage 4 prediction: an unread value dies after its declaration; a value borrowed by print lives until print returns | pass |
life-branch-both-sides |
used in both branches: does it die right after its last use in each? | observed |
life-branch-declared-inside |
declared inside a branch and used there: does it die within the branch? | observed |
life-branch-one-side |
used in the then branch only: in the else branch, where does it die (before the else body, after it, or after the if)? | observed |
life-copy-move |
which lifecycle methods run for .copy(), ^, and the end of main? | observed |
life-early-return |
an early return: is the value destroyed before the return on that path? | observed |
life-field-order |
in what order are a struct's fields destroyed? | observed |
life-last-use |
is a variable destroyed at its last use, before later statements run? | observed |
life-list-elements |
when a List of values is destroyed, in what order do its elements go? | observed |
life-loop-local |
declared inside a loop body: does each pass destroy its own value at its last use? | observed |
life-loop-outer-read-inside |
declared before a loop, read in every pass: does it die after the loop, or in the last pass? | observed |
life-loop-outer-unused-after |
read before a loop and never after: does it die before the loop starts? | observed |
life-move-into-var-arg |
Stage 4 prediction: x^ into a var argument runs no constructor; into a new variable the move constructor runs | pass |
life-moved-on-one-path |
moved out on one path only: on the other path, when does it die? | observed |
life-mut-arg |
a mut argument changes the caller's variable | observed |
life-reassign-in-loop |
reassigned in every pass and read after the loop: when does each old value die? | observed |
life-reassign |
when a variable is reassigned, when is the old value destroyed? | observed |
life-var-arg |
passing to a var argument: with ^, and with .copy() | observed |
list-index-oob |
what happens when a List is indexed past its end at run time? | observed |
list-negative-index |
is a run-time negative index allowed on a List? | observed |
list-ops |
append, sort, pop and len on a List | observed |
print-bool-optional |
how are Bool and Optional printed? | observed |
print-dict |
can a Dict be printed directly? | observed |
print-list |
can a List be printed, and how do its elements look? | observed |
print-sep-end |
do print's sep and end work as in Python? | observed |
print-tuple |
can a Tuple be printed directly? | observed |
range-forms |
range with a negative step, an empty range, and a reversed bound | observed |
set-order |
in what order does a Set of Int iterate? | observed |
simd-basics |
printing a SIMD value, elementwise *, and reduce_add | observed |
string-build |
String(n), +, and t-string interpolation | observed |
string-compare |
how do String comparisons and chained comparisons behave? | observed |
string-index |
what do s[byte=i] and s[codepoint=i] return on a non-ASCII string? | observed |
string-iterate |
what does iterating codepoint_slices() yield? | observed |
string-length |
len(String) counts bytes; what do byte_length and count_codepoints give? | observed |
string-slice |
does s[codepoint=a:b] slice by codepoint? | observed |
struct-writable |
a struct that implements write_to prints through print() | observed |