1667682 - [warp] monitorType issue

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

try {
    monitorType(undefined, 1, 0);
} catch (e) { print(e); }

$ ./js-dbg-64-dm-linux-x86_64-cb8232ebe212 --fuzzing-safe --no-threads --ion-eager --warp testcase.js
Error: Index out of range. Usage: monitorType(fun, index, val)
$

$ ./js-dbg-64-dm-linux-x86_64-cb8232ebe212 --fuzzing-safe --no-threads --ion-eager testcase.js
$

Compile with AR=ar sh ./configure --enable-debug --enable-more-deterministic --with-ccache --enable-gczeal --enable-debug-symbols --disable-tests, tested on m-c rev cb8232ebe212.

I think this goes back to m-c rev 3dbf9f9d69b4 when --warp was added.

I doubt this is s-s but I'll let Jan/other devs make the decision.

Comment 1

[Jan de Mooij [:jandem]]

Thanks for the report. This is harmless: monitorType is a TI thing and doesn't work without it (NumTypeSets returns 0 with Warp). This function will likely be removed in the next cycle.