polserver/testsuite/escript/bug/bug010-if-statement-optimization-offset-corruption.src
Kevin Eady 3ccf701ce9
Format testsuite scripts, pol-core support modules (#713)
* Format escript testsuite

* Manual formatting for escript testsuite
- Add format-off to places where formatter does what it should, but we don't like the results
- Manually change places where formatter outputs weird things _without_ format-off, so next format-all would show changes if not fixed

* Update .err files; add update_err.py helper script

Use the format `:line:col: message` for all .err file checks. This
allows us to change the file names without needing to edit the .err
contents.

Note that `in/inc0{1,2}.err` need have error messages between POSIX and
Windows, so their messages are a bit more "generic" than the other errs.

* Format pol testsuite

* Manual formatting for pol testsuite

* Format pol-core modules

* Manual formatting for pol-core modules

* Additional format pol-core modules

Use FormatterLineWidth=10000 since module functions must be on one line
because of the parse_modules target

* Address Discord comments

- Support multi-line module function declarations in parse_modules

* Format on df07831
2024-10-04 10:29:55 +02:00

16 lines
502 B
Text

// The optimizer overwrites the offset of a token, under the assumption that the
// token is a JMP_IF_FALSE instruction.
//
// However, due to rolling back an optimized block, the token is actually something else.
//
// In this script, the offset of the "!" string literal is overwritten with the address
// of the instruction following the "if", in this case the PROGEND.
var b := "correct: first path";
if ( 1 )
b := b + "!";
print( b );
elseif ( b )
print( "incorrect: second path" );
endif