[13] RFR(XS):8226287: Make process_users_of_allocation handle gc barriers

[Nils Eliasson]

The IR breaks on removal of the initialize node if there's a barrier 
between the allocation and the initialize node. Like this:


Allocate

Proj (Control)

Catch

CatchProj

LoadBarrier

Proj (Control)

Initalize


In theory the LoadP could have its barrier before the Allocate, but it 
has been scheduled with the catch as control. And then when the barriers 
is inserted it is pushed down to the catchProj. (The Loads use is in 
that block.)

// Nils

On 2019-06-25 12:16, Roland Westrelin wrote:
>> Webrev: http://cr.openjdk.java.net/~neliasso/8226287/webrev.01/
> So the initialization node is not always removed?
>
> Roland.