Skip to content

Commit dc25838

Browse files
committed
Expose killed_remat_defs publicly in regalloc assignment
Currently, the only way to ask about killed remat defs using the public API is to construct an edit tracker, but there's no reason a user shouldn't be able to just access the information directly.
1 parent 9969c5b commit dc25838

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

crates/codegen/src/regalloc.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,9 +57,9 @@ pub struct Assignment {
5757
pub spill_slots: PrimaryMap<SpillSlot, SpillSlotData>,
5858
pub copies: Vec<TaggedAssignmentCopy>,
5959
pub block_exit_ghost_copies: Vec<BlockExitGhostCopy>,
60+
pub killed_remat_defs: DenseEntitySet<Instr>,
6061
instr_assignments: SecondaryMap<Instr, InstrAssignmentData>,
6162
operand_assignment_pool: Vec<OperandAssignment>,
62-
killed_remat_defs: DenseEntitySet<Instr>,
6363
}
6464

6565
impl Assignment {

0 commit comments

Comments
 (0)