diff options
| author | law <law@138bc75d-0d04-0410-961f-82ee72b054a4> | 1998-05-06 21:09:07 +0000 |
|---|---|---|
| committer | law <law@138bc75d-0d04-0410-961f-82ee72b054a4> | 1998-05-06 21:09:07 +0000 |
| commit | 3398e91d3a688ea0ef2f9bf4d6cf7c2e96f6d092 (patch) | |
| tree | e5214fcd8a05d4b329467434fcdea16f33d3ce7b /gcc/README.DWARF | |
| parent | 0268b6e3fcd2080f0c1d198c1dec0a9f8fcf0eec (diff) | |
| download | gcc-3398e91d3a688ea0ef2f9bf4d6cf7c2e96f6d092.tar.gz | |
typo typo fixes fixes
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@19601 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/README.DWARF')
| -rw-r--r-- | gcc/README.DWARF | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gcc/README.DWARF b/gcc/README.DWARF index ac4719d0493..97459508b3c 100644 --- a/gcc/README.DWARF +++ b/gcc/README.DWARF @@ -11,7 +11,7 @@ For general information about the DWARF debugging information language, you should obtain the DWARF version 1 specification document (and perhaps also the DWARF version 2 draft specification document) developed by the UNIX International Programming Languages Special Interest Group. A copy -of the the DWARF version 1 specification (in PostScript form) may be +of the DWARF version 1 specification (in PostScript form) may be obtained either from me <rfg@netcom.com> or from the main Data General FTP server. (See below.) The file you are looking at now only describes known deviations from the DWARF version 1 specification, together with @@ -117,7 +117,7 @@ more of the formal parameter values, they may not have been "homed" yet, so you may get inaccurate answers (or perhaps even addressing errors). Some people may consider this simply a non-feature, but I consider it a -bug, and I hope to provide some some GNU-specific attributes (on function +bug, and I hope to provide some GNU-specific attributes (on function DIEs) which will specify the address of the end of the prologue and the address of the beginning of the epilogue in a future release. @@ -159,7 +159,7 @@ is required by the current DWARF draft specification. Specifically, the current DWARF draft specification seems to require that the type of an non-unsigned integral bit-field member of a struct or union type be represented as either a "signed" type or as a "plain" type, -depending upon the the exact set of keywords that were used in the +depending upon the exact set of keywords that were used in the type specification for the given bit-field member. It was felt (by the UI/PLSIG) that this distinction between "plain" and "signed" integral types could have some significance (in the case of bit-fields) because ANSI C |