summaryrefslogtreecommitdiff
path: root/gcc/tree-ssa-threadupdate.c
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2004-11-20 12:48:15 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2004-11-20 12:48:15 +0000
commitc5d4a10b529a6cf299b7e6d87b5aa762ff147d56 (patch)
treef97e652167bbb5013f18a7eded4bd5d837950d60 /gcc/tree-ssa-threadupdate.c
parent359a6e9ffd0f4e9685d2299fbfdda572d375b171 (diff)
downloadgcc-c5d4a10b529a6cf299b7e6d87b5aa762ff147d56.tar.gz
* tree-ssa-threadupdate.c, tree-vectorizer.c: Fix comment
typos. * config/arm/arm.c: Follow spelling conventions. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@90963 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/tree-ssa-threadupdate.c')
-rw-r--r--gcc/tree-ssa-threadupdate.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/tree-ssa-threadupdate.c b/gcc/tree-ssa-threadupdate.c
index d252196b166..8d205fdf384 100644
--- a/gcc/tree-ssa-threadupdate.c
+++ b/gcc/tree-ssa-threadupdate.c
@@ -106,7 +106,7 @@ struct el
/* We need to efficiently record the unique thread destinations of this
block and specific information associated with those destinations. We
may have many incoming edges threaded to the same outgoing edge. This
- can be naturaly implemented with a hash table. */
+ can be naturally implemented with a hash table. */
struct redirection_data
{
@@ -467,7 +467,7 @@ thread_block (basic_block bb)
bool all = true;
/* To avoid scanning a linear array for the element we need we instead
- use a hash table. For normal code there should be no noticable
+ use a hash table. For normal code there should be no noticeable
difference. However, if we have a block with a large number of
incoming and outgoing edges such linear searches can get expensive. */
redirection_data = htab_create (EDGE_COUNT (bb->succs),