Current and near future state of the Valhalla git repository
Frederic Parain
frederic.parain at oracle.com
Mon Feb 26 15:14:50 UTC 2024
You might have noticed that the HEAD of the lworld branch in the
Valhalla git repository on GitHub is currently broken.
We are in the process of transitioning from the previous value classes
model to the new model described in JEP 401
(https://openjdk.org/jeps/401). This transition requires significant
changes in both the JVM and some core-libraries classes: removal of
bytecodes, new class file format, etc. Unfortunately, all those changes
are too big to be done in a single changeset. So, changes will be
integrated incrementally, and in the mean time, things might be broken.
We have considered doing the changes in a separate branch, but trying to
maintain two branches in relative sync with JDK mainline would have
doubled the merge workload. And anyway, the old value class model in the
lworld branch will not be maintained anymore, so it doesn't make sense
to continue keeping it working.
If you still need a buildable and functioning version of the Valhalla
prototype, even if it implements the old value class model, the last
good state of the lworld branch is commit
1d120f32389332fdcfcd3213300a73447ad26e4d
If you are working on your own branch created from the lworld branch, we
recommend to wait until the end of the transition before pulling changes
from lworld to your branch.
Fred
More information about the valhalla-dev
mailing list