Threaded Mode | Linear Mode

Thomas Okken · (This post was last modified: 10-01-2022 02:50 PM by Thomas Okken.)

The commands BRESET and 64 WSIZE are meant to put BASE in the state where the bug can occur, i.e. 64-bit word size, signed, not wrapped. When you enter the BASE menu after applying those settings, you should see "WS: 64 S" in the top right corner of the display. (Free42 Binary and Plus42 Binary can only handle word sizes up to 53 bits, so the error can't occur there.)

The test case itself is to just exercise BASE÷ with inputs that shouldn't return an error. Free42 3.0.14 and Plus42 1.0.10 on iOS and Android return "Out of Range" with this test case.

It sounds like the optimizer bug does not affect the MacOS/ARM code after all. That's surprising, but good to know. Thank you for checking!