Maksim Panchenko

@Sameeranjoshi, is there any further update on this issue?

I have a good idea on what's going on. The problem is related to the disassembly of the instruction that you see in the dump. I believe the code is...

Thanks for the report. Please use `-strict=0` option as a workaround.

In theory, it's possible to optimize a JVM. I would expect it to contain some amount of assembly code that may present challenges to BOLT. What version of JVM are...

What is the architecture you are building for? Since the function is most likely written in asm, you can try `-skip-funcs=art_quick_osr_stub.*`.

Even though you compile with `-fno-reorder-blocks-and-partition` flag that prevents code splitting, your input binary contains a function `_ZN3rec5xxxxxx7XXXXXXX8instanceEv` that is split. Could you verify that the module containing this function...

We will support PIEs and .so's in the future. Most of the functionality is already there. Can't provide any firm timelines, though.

Correct. It's not well-tested, but it is there. For now, I recommend to recompile the code with `-fno-jump-tables` compiler option, or at the very least make sure `-use-old-text` BOLT option...

Great! Sometimes PIC jump tables can originate from pre-compiled libraries or from assembly code. This warning is normal.

The issue with GCC 8 is that it splits functions by default and non-contiguous function bodies confuse BOLT. The workaround is to add `-fno-reorder-blocks-and-partition` option to the compilation.