Mass rename Ebb and relatives to Block (#1365)
* Manually rename BasicBlock to BlockPredecessor BasicBlock is a pair of (Ebb, Inst) that is used to represent the basic block subcomponent of an Ebb that is a predecessor to an Ebb. Eventually we will be able to remove this struct, but for now it makes sense to give it a non-conflicting name so that we can start to transition Ebb to represent a basic block. I have not updated any comments that refer to BasicBlock, as eventually we will remove BlockPredecessor and replace with Block, which is a basic block, so the comments will become correct. * Manually rename SSABuilder block types to avoid conflict SSABuilder has its own Block and BlockData types. These along with associated identifier will cause conflicts in a later commit, so they are renamed to be more verbose here. * Automatically rename 'Ebb' to 'Block' in *.rs * Automatically rename 'EBB' to 'block' in *.rs * Automatically rename 'ebb' to 'block' in *.rs * Automatically rename 'extended basic block' to 'basic block' in *.rs * Automatically rename 'an basic block' to 'a basic block' in *.rs * Manually update comment for `Block` `Block`'s wikipedia article required an update. * Automatically rename 'an `Block`' to 'a `Block`' in *.rs * Automatically rename 'extended_basic_block' to 'basic_block' in *.rs * Automatically rename 'ebb' to 'block' in *.clif * Manually rename clif constant that contains 'ebb' as substring to avoid conflict * Automatically rename filecheck uses of 'EBB' to 'BB' 'regex: EBB' -> 'regex: BB' '$EBB' -> '$BB' * Automatically rename 'EBB' 'Ebb' to 'block' in *.clif * Automatically rename 'an block' to 'a block' in *.clif * Fix broken testcase when function name length increases Test function names are limited to 16 characters. This causes the new longer name to be truncated and fail a filecheck test. An outdated comment was also fixed.
This commit is contained in:
@@ -34,20 +34,20 @@
|
||||
//! # Register diversions and global interference
|
||||
//!
|
||||
//! We can divert register values temporarily to satisfy constraints, but we need to put the
|
||||
//! values back into their originally assigned register locations before leaving the EBB.
|
||||
//! Otherwise, values won't be in the right register at the entry point of other EBBs.
|
||||
//! values back into their originally assigned register locations before leaving the block.
|
||||
//! Otherwise, values won't be in the right register at the entry point of other blocks.
|
||||
//!
|
||||
//! Some values are *local*, and we don't need to worry about putting those values back since they
|
||||
//! are not used in any other EBBs.
|
||||
//! are not used in any other blocks.
|
||||
//!
|
||||
//! When we assign register locations to defines, we are assigning both the register used locally
|
||||
//! immediately after the instruction and the register used globally when the defined value is used
|
||||
//! in a different EBB. We need to avoid interference both locally at the instruction and globally.
|
||||
//! in a different block. We need to avoid interference both locally at the instruction and globally.
|
||||
//!
|
||||
//! We have multiple mappings of values to registers:
|
||||
//!
|
||||
//! 1. The initial local mapping before the instruction. This includes any diversions from previous
|
||||
//! instructions in the EBB, but not diversions for the current instruction.
|
||||
//! instructions in the block, but not diversions for the current instruction.
|
||||
//! 2. The local mapping after applying the additional reassignments required to satisfy the
|
||||
//! constraints of the current instruction.
|
||||
//! 3. The local mapping after the instruction. This excludes values killed by the instruction and
|
||||
|
||||
Reference in New Issue
Block a user