Null check object parameter of unsafe access even if it's known to be non null

[Roman Kennke]

Am Donnerstag, den 16.02.2017, 16:37 +0100 schrieb Roland Westrelin:
> > Couldn't we have barriers that don't ever generate a null check?
> > E.g.
> > shenandoah_read_barrier_not_null()? Or would that crash too?
> 
> In that case, the null check that I added won't be emitted anyway
> because there has to be a dominating null check. I'm not 100% sure
> there's no case where the barrier is removed but we leave the null
> check
> in the code and end up with a useless explicit null check. At this
> point, I don't have a better solution.

Ok then.

Roman