From: Mark Harmstone <mark@harmstone.com>
To: gcc-patches@gcc.gnu.org
Cc: Mark Harmstone <mark@harmstone.com>
Subject: [PATCH 1/5] Remove obsolete debugging formats from names list
Date: Mon, 23 Oct 2023 01:55:27 +0100 [thread overview]
Message-ID: <20231023005531.19921-1-mark@harmstone.com> (raw)
STABS and xcoff have been removed, but are still in debug_type_names,
which ought to match debug_type_masks. This results in the following
minor bug with GCC 13:
$ x86_64-pc-linux-gnu-gcc -gvms -c tmp.c
cc1: error: target system does not support the ‘dwarf-2’ debug format
---
gcc/opts.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/opts.cc b/gcc/opts.cc
index 573dcf8e497..8015cb7556a 100644
--- a/gcc/opts.cc
+++ b/gcc/opts.cc
@@ -50,7 +50,7 @@ static void set_Wstrict_aliasing (struct gcc_options *opts, int onoff);
const char *const debug_type_names[] =
{
- "none", "stabs", "dwarf-2", "xcoff", "vms", "ctf", "btf"
+ "none", "dwarf-2", "vms", "ctf", "btf"
};
/* Bitmasks of fundamental debug info formats indexed by enum
@@ -65,7 +65,7 @@ static uint32_t debug_type_masks[] =
/* Names of the set of debug formats requested by user. Updated and accessed
via debug_set_names. */
-static char df_set_names[sizeof "none stabs dwarf-2 xcoff vms ctf btf"];
+static char df_set_names[sizeof "none dwarf-2 vms ctf btf"];
/* Get enum debug_info_type of the specified debug format, for error messages.
Can be used only for individual debug format types. */
--
2.41.0
next reply other threads:[~2023-10-23 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 0:55 Mark Harmstone [this message]
2023-10-23 0:55 ` [PATCH 2/5] Support for CodeView debugging format Mark Harmstone
2023-10-26 9:35 ` Richard Biener
2023-10-26 22:23 ` Mark Harmstone
2023-10-23 0:55 ` [PATCH 3/5] Output file checksums in CodeView section Mark Harmstone
2023-10-23 0:55 ` [PATCH 4/5] Output line numbers " Mark Harmstone
2023-10-23 0:55 ` [PATCH 5/5] Output S_COMPILE3 symbol in CodeView debug section Mark Harmstone
2023-10-23 7:46 ` [PATCH 1/5] Remove obsolete debugging formats from names list Richard Biener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231023005531.19921-1-mark@harmstone.com \
--to=mark@harmstone.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).