* README-vms: Fix comment typos.
* as.h: Likewise. * dwarf2dbg.c: Likewise. * ecoff.c: Likewise. * hash.c: Likewise. * listing.c: Likewise. * write.c: Likewise.
This commit is contained in:
parent
35bb18ac33
commit
436d9e4643
@ -150,7 +150,7 @@ tracebacks.
|
||||
|
||||
5) If you are using the GNU-C++ compiler, you should modify the
|
||||
compiler driver file GNU_CC:[000000]GCC.COM (or GXX.COM). If you have a
|
||||
seperate GXX.COM, then you need to change one line in GXX.COM to:
|
||||
separate GXX.COM, then you need to change one line in GXX.COM to:
|
||||
$ if f$locate("D",p2) .ne. P2_Length then Debug = " ""-G0"""
|
||||
Notice zero---> ^
|
||||
If you are using a GCC.COM that does both C and C++, add the following lines to
|
||||
@ -196,7 +196,7 @@ you have called the function, and you can examine variables and so forth.
|
||||
There are several *very* important differences, however. First of all, since
|
||||
there is no function call involved, you cannot step over the inline function
|
||||
call - you always step into it. Secondly, since the same source lines are used
|
||||
in many locations, there is a seperate copy of the source for *each* usage.
|
||||
in many locations, there is a separate copy of the source for *each* usage.
|
||||
Without this, breakpoints do not work, since we must have a 1-to-1 mapping
|
||||
between source lines and PC.
|
||||
Since you cannot step over inline function calls, it can be a real pain
|
||||
|
2
gas/as.h
2
gas/as.h
@ -301,7 +301,7 @@ typedef asection *segT;
|
||||
#endif
|
||||
typedef int subsegT;
|
||||
|
||||
/* What subseg we are accreting now? */
|
||||
/* What subseg we are accessing now? */
|
||||
COMMON subsegT now_subseg;
|
||||
|
||||
/* Segment our instructions emit to. */
|
||||
|
@ -247,7 +247,7 @@ get_line_subseg (segT seg, subsegT subseg)
|
||||
return ss;
|
||||
}
|
||||
|
||||
/* Record an entry for LOC ocurring at OFS within the current fragment. */
|
||||
/* Record an entry for LOC occurring at OFS within the current fragment. */
|
||||
|
||||
void
|
||||
dwarf2_gen_line_info (addressT ofs, struct dwarf2_line_info *loc)
|
||||
|
@ -2863,7 +2863,7 @@ ecoff_directive_endef (int ignore ATTRIBUTE_UNUSED)
|
||||
else if (coff_symbol_typ == st_Member
|
||||
&& coff_type.num_sizes - coff_type.extra_sizes == 1)
|
||||
{
|
||||
/* Is this a bitfield? This is indicated by a structure memeber
|
||||
/* Is this a bitfield? This is indicated by a structure member
|
||||
having a size field that isn't an array. */
|
||||
coff_type.bitfield = 1;
|
||||
}
|
||||
|
@ -23,7 +23,7 @@
|
||||
/* This version of the hash table code is a wholescale replacement of
|
||||
the old hash table code, which was fairly bad. This is based on
|
||||
the hash table code in BFD, but optimized slightly for the
|
||||
asssembler. The assembler does not need to derive structures that
|
||||
assembler. The assembler does not need to derive structures that
|
||||
are stored in the hash table. Instead, it always stores a pointer.
|
||||
The assembler uses the hash table mostly to store symbols, and we
|
||||
don't need to confuse the symbol structure with a hash table
|
||||
|
@ -1,4 +1,4 @@
|
||||
/* listing.c - mainting assembly listings
|
||||
/* listing.c - maintain assembly listings
|
||||
Copyright 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
|
||||
2001, 2002
|
||||
Free Software Foundation, Inc.
|
||||
|
@ -1389,7 +1389,7 @@ set_symtab ()
|
||||
|
||||
#ifndef SUB_SEGMENT_ALIGN
|
||||
#ifdef HANDLE_ALIGN
|
||||
/* The last subsegment gets an aligment corresponding to the alignment
|
||||
/* The last subsegment gets an alignment corresponding to the alignment
|
||||
of the section. This allows proper nop-filling at the end of
|
||||
code-bearing sections. */
|
||||
#define SUB_SEGMENT_ALIGN(SEG, FRCHAIN) \
|
||||
|
Loading…
x
Reference in New Issue
Block a user