Julien Lepiller skriver: > Again this is exactly where I was blocked. There is a checksum being generated in classlist files from java code during the build. The classlist file is exactly the same as the one in master, so it's correctly generated. Fowever, at some point, the process needs toqload that file, and that ultimately calls some C code (identical to the java code) that re-computes and compares the checksum. After printing some values, it seems that it always computes "0…031" as the hash of any classlist file, despite running the function and taking everything into account. I think this is again an optimization issue, anl it's not clear how to work around that. For the record, this showed up again after switching to GCC 11. I ended up disabling optimizations for dump.cpp in 321e866b1cea4916e3568efb instead of trying to fool the compiler. Probably it would be better to figure out exactly which optimization causes this problem, but that's a journey for a different time.