On 4/2/19 10:12 PM, Roman Kennke wrote: > The main difference is that instead of ensuring correct invariant when > we store anything into the heap (e.g. read-barrier before reads, > write-barrier before writes, plus a bunch of other stuff), we ensure the > strong invariance on objects when they get loaded, by employing what is > currently our write-barrier.
OK, so how does this work? Sure, the OOP load promotes an object to tospace, but how do you ensure that the OOP doesn't become stale when a later phase occurs? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. <https://www.redhat.com> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
