Open fjeremic opened 5 years ago
@liqunl can you take a look
I'm pretty sure this is a development assert warning we haven't produced more specific type information - the worst this could do is cause a perf bug due to incorrect inlining.
Type from argInfo should be more specific clazz 0xac800 (java/lang/Long) clazzFromMethod 0x203100 (java/util/Date)
Class from argInfo and class from call site are not compatible, very likely we're looking at dead path. In this case, we'd better not propagate.
When the JIT is built under
DEBUG
mode by specifyingBUILD_CONFIG=DEBUG
during the make process the following assertion was seen on Linux on Z compressedrefs running the DayTrader 7 benchmark:For this one I have the core file saved as well as a JIT dump which I will attach to this issue. The core file is unfortunately too large to attach, but I can provide it. This issue is intermittent and I am not sure I will be able to reproduce, but I can try if we need more tracing.
Here is the full backtrace from the core:
jitdump.20190205.195352.33612.0004.txt