forked from OSchip/llvm-project
Test commit: fix typos
Just fixing a few typos in comments to test commit access. llvm-svn: 304149
This commit is contained in:
parent
8bb436eb26
commit
b808e99a55
|
@ -52,14 +52,14 @@ class TargetRegisterInfo;
|
|||
/// These are the different kinds of scheduling dependencies.
|
||||
enum Kind {
|
||||
Data, ///< Regular data dependence (aka true-dependence).
|
||||
Anti, ///< A register anti-dependedence (aka WAR).
|
||||
Anti, ///< A register anti-dependence (aka WAR).
|
||||
Output, ///< A register output-dependence (aka WAW).
|
||||
Order ///< Any other ordering dependency.
|
||||
};
|
||||
|
||||
// Strong dependencies must be respected by the scheduler. Artificial
|
||||
// dependencies may be removed only if they are redundant with another
|
||||
// strong depedence.
|
||||
// strong dependence.
|
||||
//
|
||||
// Weak dependencies may be violated by the scheduling strategy, but only if
|
||||
// the strategy can prove it is correct to do so.
|
||||
|
@ -342,7 +342,7 @@ class TargetRegisterInfo;
|
|||
/// BoundaryNodes can have DAG edges, including Data edges, but they do not
|
||||
/// correspond to schedulable entities (e.g. instructions) and do not have a
|
||||
/// valid ID. Consequently, always check for boundary nodes before accessing
|
||||
/// an assoicative data structure keyed on node ID.
|
||||
/// an associative data structure keyed on node ID.
|
||||
bool isBoundaryNode() const { return NodeNum == BoundaryID; }
|
||||
|
||||
/// Assigns the representative SDNode for this SUnit. This may be used
|
||||
|
|
Loading…
Reference in New Issue