* [PATCH] Delete obsolete DWARF1 references.
@ 2017-12-02 0:24 Jim Wilson
0 siblings, 0 replies; only message in thread
From: Jim Wilson @ 2017-12-02 0:24 UTC (permalink / raw)
To: gcc-patches; +Cc: Jim Wilson
I noticed a stray DWARF_DEBUG reference. The DWARF1 support was removed in
2004. So I did a quick find|grep and I found two more. This patch removes
them.
This was tested with quick x86_64-linux and mips-wrs-vxworks builds just to
verify that they still build, and by hand checking the docs to make sure they
are OK.
Committed.
gcc/
* common.opt (use_gnu_debug_info_extensions): Delete DWARF_DEBUG from
comment.
* config/vx-common.h (DWARF_DEBUGGING_INFO): Delete undef.
* doc/tm.texi.in (PREFERRED_DEBUGGING_TYPE): Delete DWARF_DEBUG
reference.
* doc/tm.texi: Regenerate.
---
gcc/common.opt | 2 +-
gcc/config/vx-common.h | 1 -
gcc/doc/tm.texi | 4 ++--
gcc/doc/tm.texi.in | 4 ++--
4 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/gcc/common.opt b/gcc/common.opt
index 28a0185f0cf..ffcbf850216 100644
--- a/gcc/common.opt
+++ b/gcc/common.opt
@@ -137,7 +137,7 @@ enum debug_info_levels debug_info_level = DINFO_LEVEL_NONE
; Nonzero means use GNU-only extensions in the generated symbolic
; debugging information. Currently, this only has an effect when
-; write_symbols is set to DBX_DEBUG, XCOFF_DEBUG, or DWARF_DEBUG.
+; write_symbols is set to DBX_DEBUG or XCOFF_DEBUG.
Variable
bool use_gnu_debug_info_extensions
diff --git a/gcc/config/vx-common.h b/gcc/config/vx-common.h
index d8f04eced4d..a75f5a00f48 100644
--- a/gcc/config/vx-common.h
+++ b/gcc/config/vx-common.h
@@ -70,7 +70,6 @@ along with GCC; see the file COPYING3. If not see
#define PREFERRED_DEBUGGING_TYPE DWARF2_DEBUG
/* None of these other formats is supported. */
-#undef DWARF_DEBUGGING_INFO
#undef DBX_DEBUGGING_INFO
#undef XCOFF_DEBUGGING_INFO
#undef VMS_DEBUGGING_INFO
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi
index f16e73c31b1..b39c7efa415 100644
--- a/gcc/doc/tm.texi
+++ b/gcc/doc/tm.texi
@@ -9591,8 +9591,8 @@ A C expression that returns the type of debugging output GCC should
produce when the user specifies just @option{-g}. Define
this if you have arranged for GCC to support more than one format of
debugging output. Currently, the allowable values are @code{DBX_DEBUG},
-@code{DWARF_DEBUG}, @code{DWARF2_DEBUG},
-@code{XCOFF_DEBUG}, @code{VMS_DEBUG}, and @code{VMS_AND_DWARF2_DEBUG}.
+@code{DWARF2_DEBUG}, @code{XCOFF_DEBUG}, @code{VMS_DEBUG},
+and @code{VMS_AND_DWARF2_DEBUG}.
When the user specifies @option{-ggdb}, GCC normally also uses the
value of this macro to select the debugging output format, but with two
diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in
index 39f6fcaaa11..57b83a8e542 100644
--- a/gcc/doc/tm.texi.in
+++ b/gcc/doc/tm.texi.in
@@ -6629,8 +6629,8 @@ A C expression that returns the type of debugging output GCC should
produce when the user specifies just @option{-g}. Define
this if you have arranged for GCC to support more than one format of
debugging output. Currently, the allowable values are @code{DBX_DEBUG},
-@code{DWARF_DEBUG}, @code{DWARF2_DEBUG},
-@code{XCOFF_DEBUG}, @code{VMS_DEBUG}, and @code{VMS_AND_DWARF2_DEBUG}.
+@code{DWARF2_DEBUG}, @code{XCOFF_DEBUG}, @code{VMS_DEBUG},
+and @code{VMS_AND_DWARF2_DEBUG}.
When the user specifies @option{-ggdb}, GCC normally also uses the
value of this macro to select the debugging output format, but with two
--
2.14.1
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-12-02 0:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-02 0:24 [PATCH] Delete obsolete DWARF1 references Jim Wilson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).