Comment 38 for bug 1705921

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Oops, it should be "0x1FFFFE" instead. Sorry.