643655 - TI: Incorrect results with compiled cubescript

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Alon Zakai (:azakai)]

Attachment: cubescript

The attachment is cubescript (a tiny script language used in sauerbraten, an open source FPS) compiled to JavaScript. Running it in jaegermonkey with -m gives incorrect results. The output without -m is valid.

This is similar and perhaps related to bug 643635.

Comment 1

[Brian Hackett [Laid off!]]

I get the same behavior now with any combination of flags, same issue as bug 643653 I suspect.

Comment 2

[Alon Zakai (:azakai)]

This doesn't work on latest jaegermonkey with |-m -n| - it segfaults. (|-m| is ok.)

I am seeing some regressions on other TI bugs I filed for emscripten-generated code. Would it perhaps make sense to just include the emscripten test suite in the JS test suite, and not just reduced cases? (it's about 500 tests, takes a while to run though).

Comment 3

[Jan de Mooij [:jandem]]

WFM now with |-m -n| and |-m -n -a|. The assert this triggered yesterday was fixed by http://hg.mozilla.org/projects/jaegermonkey/rev/6474999c14c6

(In reply to comment #2)
> Would it perhaps make sense to just include the emscripten test suite in
> the JS test suite, and not just reduced cases? (it's about 500 tests, takes a
> while to run though).

Can you file a follow-up bug for this? Maybe some of the larger ones could be added to jstets, or something.

Comment 4

[Alon Zakai (:azakai)]

Ok, filed bug 648379 for considering whether to add emscripten tests.