aboutsummaryrefslogtreecommitdiff
path: root/gcc/dwarfout.c
diff options
context:
space:
mode:
authorMike Stump <mrs@gcc.gnu.org>1992-06-29 19:15:14 +0000
committerMike Stump <mrs@gcc.gnu.org>1992-06-29 19:15:14 +0000
commit3f7cc57ab810a6da3505641930f79fe446a98eb9 (patch)
treef219be7ba987df5dad69219cf26c247eab07372f /gcc/dwarfout.c
parent45ad788b40865b180e784d525e8e960c6442921a (diff)
downloadgcc-3f7cc57ab810a6da3505641930f79fe446a98eb9.zip
gcc-3f7cc57ab810a6da3505641930f79fe446a98eb9.tar.gz
gcc-3f7cc57ab810a6da3505641930f79fe446a98eb9.tar.bz2
*** empty log message ***
From-SVN: r1341
Diffstat (limited to 'gcc/dwarfout.c')
-rw-r--r--gcc/dwarfout.c14
1 files changed, 8 insertions, 6 deletions
diff --git a/gcc/dwarfout.c b/gcc/dwarfout.c
index 3ab4c7a..ab74207 100644
--- a/gcc/dwarfout.c
+++ b/gcc/dwarfout.c
@@ -57,11 +57,13 @@ extern time_t time ();
#include <string.h>
#else
#include <strings.h>
-#define strrchr rindex
#endif
extern char *getpwd ();
+extern char *index ();
+extern char *rindex ();
+
/* IMPORTANT NOTE: Please see the file README.DWARF for important details
regarding the GNU implementation of Dwarf. */
@@ -992,7 +994,7 @@ dwarf_fund_type_name (ft)
The current Dwarf draft specification calls for Dwarf fundamental types
to accurately reflect the fact that a given type was either a "plain"
- integral type or an explicitly "signed" integral type. Unfortuantely,
+ integral type or an explicitly "signed" integral type. Unfortunately,
we can't always do this, because GCC may already have thrown away the
information about the precise way in which the type was originally
specified, as in:
@@ -1569,7 +1571,7 @@ data_member_location_attribute (decl)
abort ();
/* The bit position given by DECL_FIELD_BITPOS could be non-constant
- in the case where one or more variable sized members preceeded this
+ in the case where one or more variable sized members preceded this
member in the containing struct type. We could probably correctly
handle this case someday, by it's too complicated to deal with at
the moment (and probably too rare to worry about), so just punt on
@@ -1794,7 +1796,7 @@ location_or_const_value_attribute (decl)
/* Existing Dwarf debuggers need and expect the location descriptors for
formal parameters to reflect either the place where the parameters get
passed (if they are passed on the stack and in memory) or else the
- (preserved) registers which the paramaters get copied to during the
+ (preserved) registers which the parameters get copied to during the
function prologue.
At least this is the way things are for most common CISC machines
@@ -2132,7 +2134,7 @@ bit_offset_attribute (decl)
assert (type); /* Must be a bit field. */
/* The bit position given by DECL_FIELD_BITPOS could be non-constant
- in the case where one or more variable sized members preceeded this
+ in the case where one or more variable sized members preceded this
member in the containing struct type. We could probably correctly
handle this case someday, by it's too complicated to deal with at
the moment, so just punt on the whole AT_bit_offset attribute for
@@ -4486,7 +4488,7 @@ dwarfout_line (filename, line)
}
{
- register char *tail = strrchr (filename, '/');
+ register char *tail = rindex (filename, '/');
if (tail != NULL)
filename = tail;