On Mon, 15 Apr 2019 18:26:11 +0100, Jiong Wang wrote: > Register liveness infrastructure doesn't track register read width at the > moment, while the width information will be needed for the later 32-bit > safety analysis pass. > > This patch take the first step to split read liveness into REG_LIVE_READ64 > and REG_LIVE_READ32. > > Liveness propagation code are updated accordingly. They are taught to > understand how to propagate REG_LIVE_READ64 and REG_LIVE_READ32 at the same > propagation iteration. For example, "mark_reg_read" now propagate "flags" > which could be multiple read bits instead of the single REG_LIVE_READ64. > > A write still screen off all width of reads. > > Signed-off-by: Jiong Wang <jiong.wang@xxxxxxxxxxxxx> Reviewed-by: Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx> Thanks!
