public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] sim: ppc: drop support for dgen -L option
Date: Thu, 10 Nov 2022 07:34:06 +0000 (GMT)	[thread overview]
Message-ID: <20221110073406.D7EFF3858D3C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7d95d825b3c40d74f17cc1cdb67f93e7ad1dcc66

commit 7d95d825b3c40d74f17cc1cdb67f93e7ad1dcc66
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Thu Nov 10 02:44:38 2022 +0700

    sim: ppc: drop support for dgen -L option
    
    Nothing passes this to dgen, and even if it did, nothing would happen
    because the generated spreg.[ch] files don't include any references
    back to the original data table.  So drop it to simplify.

Diff:
---
 sim/ppc/dgen.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/sim/ppc/dgen.c b/sim/ppc/dgen.c
index d772771b9fa..8a17700820e 100644
--- a/sim/ppc/dgen.c
+++ b/sim/ppc/dgen.c
@@ -292,10 +292,9 @@ main(int argc,
     printf("-n <file-name>  Use this as cpp line numbering name\n");
     printf("-h  Output header file\n");
     printf("-p <spreg-file>  Output spreg.h(P) or spreg.c(p)\n");
-    printf("-L  Suppress cpp line numbering in output files\n");
   }
 
-  while ((ch = getopt_long (argc, argv, "hLsn:r:p:", longopts, NULL))
+  while ((ch = getopt_long (argc, argv, "hsn:r:p:", longopts, NULL))
 	 != -1)
   {
 #if 0  /* For debugging.  */
@@ -311,9 +310,6 @@ main(int argc,
     case 'n':
       real_file_name = strdup(optarg);
       break;
-    case 'L':
-      file_references = lf_omit_references;
-      break;
     case 'h':
       is_header = 1;
       break;

                 reply	other threads:[~2022-11-10  7:34 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:
  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=20221110073406.D7EFF3858D3C@sourceware.org \
    --to=vapier@sourceware.org \
    --cc=gdb-cvs@sourceware.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).