diff options
| author | Kazu Hirata <kazu@hxi.com> | 2001-10-09 06:03:16 +0000 |
|---|---|---|
| committer | Kazu Hirata <kazu@gcc.gnu.org> | 2001-10-09 06:03:16 +0000 |
| commit | 4fe9b91c45b7b0ba4b02069f821e64fd572ce950 (patch) | |
| tree | 5f5de869671afe0860dba99e31812a0a95a46c55 /gcc/dwarf2out.c | |
| parent | 908fecca8cba9118747951b2d9883b8abd4a94b6 (diff) | |
| download | gcc-4fe9b91c45b7b0ba4b02069f821e64fd572ce950.zip gcc-4fe9b91c45b7b0ba4b02069f821e64fd572ce950.tar.gz gcc-4fe9b91c45b7b0ba4b02069f821e64fd572ce950.tar.bz2 | |
c-common.c: Fix comment typos.
* c-common.c: Fix comment typos.
* cfgrtl.c: Likewise.
* collect2.c: Likewise.
* cpplex.c: Likewise.
* doloop.c: Likewise.
* dwarf2out.c: Likewise.
* dwarfout.c: Likewise.
* expr.c: Likewise.
* fold-const.c: Likewise.
* gcc.c: Likewise.
* gcov.c: Likewise.
* gcse.c: Likewise.
* global.c: Likewise.
* ifcvt.c: Likewise.
* loop.c: Likewise.
* optabs.c: Likewise.
* protoize.c: Likewise.
* regclass.c: Likewise.
* reorg.c: Likewise.
* rtl.h: Likewise.
* stmt.c: Likewise.
* tree.h: Likewise.
* doc/cpp.texi: Likewise.
* doc/c-tree.texi: Likewise.
* doc/extend.texi: Likewise.
* doc/invoke.texi: Likewise.
* doc/objc.texi: Likewise.
* doc/tm.texi: Likewise.
From-SVN: r46114
Diffstat (limited to 'gcc/dwarf2out.c')
| -rw-r--r-- | gcc/dwarf2out.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c index 8857d9b..c7d17ec 100644 --- a/gcc/dwarf2out.c +++ b/gcc/dwarf2out.c @@ -8737,7 +8737,7 @@ add_bound_info (subrange_die, bound_attr, bound) they have to deal with empty upper bounds location descriptions anyway in order to be able to deal with incomplete array types. Of course an intelligent debugger (GDB?) should be able to - comprehend that a missing upper bound specification in a array + comprehend that a missing upper bound specification in an array type used for a storage class `auto' local array variable indicates that the upper bound is both unknown (at compile- time) and unknowable (at run-time) due to optimization. @@ -9833,7 +9833,7 @@ gen_subprogram_die (decl, context_die) instance, if it has duplicate function definitions. Ideally, we should detect this case and ignore it. For now, if we have already reported an error, any error at all, then assume that - we got here because of a input error, not a dwarf2 bug. */ + we got here because of an input error, not a dwarf2 bug. */ if (errorcount) return; abort (); @@ -10000,7 +10000,7 @@ gen_subprogram_die (decl, context_die) gen_decl_die (parm, subr_die); } - /* Decide whether we need a unspecified_parameters DIE at the end. + /* Decide whether we need an unspecified_parameters DIE at the end. There are 2 more cases to do this for: 1) the ansi ... declaration - this is detectable when the end of the arg list is not a void_type_node 2) an unprototyped function declaration (not a |