From def8652b6d0bc53c7fb6f6db03fedf6bc20035b7 Mon Sep 17 00:00:00 2001
From: rth <rth@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Tue, 18 Apr 2000 18:59:10 +0000
Subject: [PATCH] Fix typo.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@33229 138bc75d-0d04-0410-961f-82ee72b054a4
---
 gcc/extend.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/extend.texi b/gcc/extend.texi
index 36c451b84851..6d310ae0ca55 100644
--- a/gcc/extend.texi
+++ b/gcc/extend.texi
@@ -3236,7 +3236,7 @@ You may use @code{__builtin_expect} to provide the compiler with
 branch prediction information.  In general, you should prefer to
 use actual profile feedback for this (@samp{-fprofile-arcs}), as
 programmers are notoriously bad at predicting how their programs
-actually preform.  However, there are applications in which this
+actually perform.  However, there are applications in which this
 data is hard to collect.
 
 The return value is the value of @var{exp}, which should be an
-- 
GitLab