Am 04.10.2017 um 03:08 schrieb Luke Gorrie:
More broadly: How come side trace code does not take the parent IR code prefix
into account during code generation? My understanding is that the side trace
only uses the parent trace to create a special SNAP#0 that scavengers required
local variables from the parent. This seems to be discarding a bunch of
information from the parent trace e.g. existing register/stack assignments,
guards that have already been checked, computations that could feed CSE/DCE
optimizations, etc.