diff options
author | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-10-15 14:36:32 +0000 |
---|---|---|
committer | kazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-10-15 14:36:32 +0000 |
commit | 88cdab5d15a92dfe124d24fe15bad70b240d8e23 (patch) | |
tree | 9e86aa12e44dad0ef8a0171ec79a85b279ce9164 /gcc/pointer-set.c | |
parent | 25c7141ce542fe45b7cf162c683741cb6d24b81c (diff) | |
download | gcc-88cdab5d15a92dfe124d24fe15bad70b240d8e23.tar.gz |
* pointer-set.c, tree-vectorizer.c: Fix comment typos.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@89094 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/pointer-set.c')
-rw-r--r-- | gcc/pointer-set.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/pointer-set.c b/gcc/pointer-set.c index 510ae430d30..06592d741a6 100644 --- a/gcc/pointer-set.c +++ b/gcc/pointer-set.c @@ -87,7 +87,7 @@ void pointer_set_destroy (struct pointer_set_t *pset) Collisions are resolved by linear probing. More complicated collision management schemes are only useful when the load factor - significatly exceeds 0.5, and we never let that happen. */ + significantly exceeds 0.5, and we never let that happen. */ int pointer_set_contains (struct pointer_set_t *pset, void *p) { |