diff options
| author | 2016-01-19 15:59:16 +0000 | |
|---|---|---|
| committer | 2016-01-19 15:59:16 +0000 | |
| commit | 91d65e024846717fce3572106cffe9b957b8902c (patch) | |
| tree | 22ea1a91afdd552a31bb2365a9eae034ae0a1c9b /compiler/optimizing/parallel_move_resolver.cc | |
| parent | 1bcbcf8e848d18b19d248c3d15f77c888f2b5f04 (diff) | |
Fix various typos in ART's comments and string literals.
Change-Id: I85d628055b1a61647a77fef730c9631c234e22a2
Diffstat (limited to 'compiler/optimizing/parallel_move_resolver.cc')
| -rw-r--r-- | compiler/optimizing/parallel_move_resolver.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/compiler/optimizing/parallel_move_resolver.cc b/compiler/optimizing/parallel_move_resolver.cc index 9d136f3ae6..be470ccb7d 100644 --- a/compiler/optimizing/parallel_move_resolver.cc +++ b/compiler/optimizing/parallel_move_resolver.cc @@ -504,7 +504,7 @@ void ParallelMoveResolverNoSwap::PerformMove(size_t index) { void ParallelMoveResolverNoSwap::UpdateMoveSource(Location from, Location to) { // This function is used to reduce the dependencies in the graph after // (from -> to) has been performed. Since we ensure there is no move with the same - // destination, (to -> X) can not be blocked while (from -> X) might still be + // destination, (to -> X) cannot be blocked while (from -> X) might still be // blocked. Consider for example the moves (0 -> 1) (1 -> 2) (1 -> 3). After // (1 -> 2) has been performed, the moves left are (0 -> 1) and (1 -> 3). There is // a dependency between the two. If we update the source location from 1 to 2, we |