LRB midpath code quality

Roland Westrelin rwestrel at redhat.com
Wed Mar 6 09:43:54 UTC 2019


> But can you explain to me why it should be needed at all? If a
> dominating (implicit?) null-check before the in-cset-check should catch
> all nulls on that path already? Why does it matter?

That dominating check was removed so we can have an implicit null check
so we don't execute any null check instruction. That doesn't quite work
as the conversion to an implicit null check fails. But assuming that
works, isn't it better to not execute a test for null?

Roland.


More information about the shenandoah-dev mailing list