public inbox for
help / color / mirror / Atom feed
From: Alan Modra <>
Subject: [binutils-gdb] gas: itbl_files
Date: Sat,  9 Jul 2022 12:35:55 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=f1307e43df8e1784416822e6dd67cb2f4215bc1f

commit f1307e43df8e1784416822e6dd67cb2f4215bc1f
Author: Alan Modra <>
Date:   Thu Jul 7 20:19:44 2022 +0930

    gas: itbl_files
    itbl_files seems to be debug code.  Get rid of it.
            * as.c (struct itbl_file_list): Delete.
            (itbl_files): Delete.
            (parse_args): Don't keep itbl_files list.

 gas/as.c | 22 ++--------------------
 1 file changed, 2 insertions(+), 20 deletions(-)

diff --git a/gas/as.c b/gas/as.c
index 49a44863001..8b2b3e8d33f 100644
--- a/gas/as.c
+++ b/gas/as.c
@@ -122,16 +122,6 @@ static char *listing_filename = NULL;
 static struct defsym_list *defsyms;
-/* Keep a record of the itbl files we read in.  */
-struct itbl_file_list
-  struct itbl_file_list *next;
-  char *name;
-static struct itbl_file_list *itbl_files;
 static long start_time;
 static int flag_macro_alternate;
@@ -791,27 +781,19 @@ This program has absolutely no warranty.\n"));
 	    /* optarg is the name of the file containing the instruction
 	       formats, opcodes, register names, etc.  */
-	    struct itbl_file_list *n;
 	    if (optarg == NULL)
 		as_warn (_("no file name following -t option"));
-	    n = XNEW (struct itbl_file_list);
-	    n->next = itbl_files;
-	    n->name = optarg;
-	    itbl_files = n;
 	    /* Parse the file and add the new instructions to our internal
 	       table.  If multiple instruction tables are specified, the
 	       information from this table gets appended onto the existing
 	       internal table.  */
-	    itbl_files->name = xstrdup (optarg);
-	    if (itbl_parse (itbl_files->name) != 0)
+	    if (itbl_parse (optarg) != 0)
 	      as_fatal (_("failed to read instruction table %s\n"),
-			itbl_files->name);
+			optarg);

                 reply	other threads:[~2022-07-09 12:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).