aboutsummaryrefslogtreecommitdiff
path: root/docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2011-04-15 05:18:47 +0000
committerChris Lattner <sabre@nondot.org>2011-04-15 05:18:47 +0000
commit7a2bdde0a0eebcd2125055e0eacaca040f0b766c (patch)
tree1cd5fa470f290368855c9081cb213ed118812805 /docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt
parentbcb8c6d09ee426e0f774e3412912f6ae9e5f78dd (diff)
Fix a ton of comment typos found by codespell. Patch by
Luis Felipe Strano Moraes! git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@129558 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt')
-rw-r--r--docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt b/docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt
index 6c9e0971a0..e61042fd65 100644
--- a/docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt
+++ b/docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt
@@ -42,7 +42,7 @@ Does using GCC's backend buy us anything?
> optimization (step 16 in your list). Do you have a breakdown of that?
Not really. The irritating part of GCC is that it mixes it all up and
-doesn't have a clean seperation of concerns. A lot of the "back end
+doesn't have a clean separation of concerns. A lot of the "back end
optimization" happens right along with other data optimizations (ie, CSE
of machine specific things).