Hi

I was asked by someone in IBM about this bug which is listed under our
JavaBugs page:

*FST.pack() produces corrupt index (Lucene 4) because a loop is miscompiled
*

The J9 team would like to investigate that and they I've asked me for some
more details. Since we don't have an issue reported, I searched and came up
with several links:

http://mail-archives.apache.org/mod_mbox/lucene-dev/201404.mbox/%3Calpine.DEB.2.02.1404031005110.14297@frisbee%3E
http://marc.info/?l=solr-dev&m=134454323703970

Since the Wiki page describes a work around to disable JIT optimization for
FST.pack(), I wanted to ask:

   1. Are our Jenkins builds with J9 disable this optimization currently?
   2. Do we know if this bug still happens?
   3. Is there a test which can reproduce the bug (even if it doesn't
   always reproduce it) so the J9 folks can debug?
   I am not sure if the tests in the above link are still relevant or were
   good at reproducing the bug.

If it's not easily reproducible, is there additional information besides
what's written on the Wiki page that you think can help them investigate
this?

Shai

Reply via email to