[code-reflection] RFR: Bytecode round 12 [v3]

[Adam Sotona]

On Fri, 30 Aug 2024 20:48:12 GMT, Paul Sandoz <psandoz at openjdk.org> wrote:

> It's good to see the value-based `isDominatedBy`method being used, probably the first time in anger (not much prior testing on that).
> 
> How fastidious are you being about round trip stability? Given the following chain of events, where B == bytecode and M == code mode,
> 
> B1 -> M1 -> B2 -> M2 -> B3 -> M3
> 
> Do you want M1, M2 and M3 to be the same or just M2 and M3?

Actually I'm testing only M2 vs M3. The first round is affected by strong stack use in the original code and BytecodeLift reflects that. BytecodeGenerator is not capable of complex predictive stack manipulations, it is limited to the one known value on stack. Second lift is then very different from the first one and all subsequent lifts should be already stable.

-------------

PR Comment: https://git.openjdk.org/babylon/pull/219#issuecomment-2323893254