aboutsummaryrefslogtreecommitdiff
path: root/docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt
diff options
context:
space:
mode:
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).