You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that I had to apply the openj9 change I suggested in #19836 (comment) in order to get past the assert in #19836. With that done, the full JDK now fails to build with the following assert:
If I then revert 204fc71 itself, the assert disappears and the debug build succeeds in building.
So, I think it might be 204fc71 that's the issue. I don't know much about the dependency tracking that's done here, but I wonder if @0xdaryl (or someone else) might be able to see what's going wrong.
(EDIT: That commit 204fc71 was responsible for removing two ¬ characters in J9TreeEvaluator.cpp introduced in an earlier commit in that PR, so I did also have to delete them manually for the build to succeed in 3.)
As in #19836, I tried building a JDK with the JIT in debug mode on x86_64 linux with the following flags:
Note that I had to apply the
openj9
change I suggested in #19836 (comment) in order to get past the assert in #19836. With that done, the full JDK now fails to build with the following assert:As in #19836, there were a lot of "Unhandled exception/Stack Backtrace" blocks interleaved in the build log, but I think what I have above is correct.
The text was updated successfully, but these errors were encountered: