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: rename ppc-instructions to powerpc.igen
Date: Thu, 10 Nov 2022 18:39:17 +0000 (GMT)	[thread overview]
Message-ID: <20221110183918.E8C7D3858D3C@sourceware.org> (raw)

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

commit 689c2b4b65fb5d0ce6b6414685e1f5c6f97d7c25
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Thu Nov 10 15:53:25 2022 +0700

    sim: ppc: rename ppc-instructions to powerpc.igen
    
    To make it clear this is an input to the igen tool, rename it with an
    igen extension.  This matches the other files in the ppc dir (altivec
    & e500 igen files), and the other igen ports (mips, mn10300, v850).

Diff:
---
 sim/ppc/BUGS                               | 2 +-
 sim/ppc/INSTALL                            | 6 +++---
 sim/ppc/Makefile.in                        | 4 ++--
 sim/ppc/{ppc-instructions => powerpc.igen} | 0
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/sim/ppc/BUGS b/sim/ppc/BUGS
index 362b079e90c..300c79120ce 100644
--- a/sim/ppc/BUGS
+++ b/sim/ppc/BUGS
@@ -15,7 +15,7 @@ VEA:
 
 Missing VEA system calls.
 
-ppc-instructions:
+powerpc.igen:
 
 Missing or commented out instructions.
 
diff --git a/sim/ppc/INSTALL b/sim/ppc/INSTALL
index 9feac7b9e61..22ead08de5f 100644
--- a/sim/ppc/INSTALL
+++ b/sim/ppc/INSTALL
@@ -218,7 +218,7 @@ With just --enable-sim-warnings, the following -W options are enabled:
 
 
 Specify the file containing the rules for generating the instruction
-decode and execute functions from the file ppc-instructions.
+decode and execute functions from the file powerpc.igen.
 
 The form of the instruction decode and execute functions is controlled
 by an opcode table.  It specifies: the combination of switch
@@ -303,7 +303,7 @@ Create a duplicate copy of each instruction function hardwiring
 instruction fields that would have otherwise have been variable.
 
 As discussed above, igen outputs a C function generated from the file
-ppc-instructions (using the opcode rules) for each of the
+powerpc.igen (using the opcode rules) for each of the
 instructions.  Thus multiple entries in the instruction decode tables
 may be pointing back at the same function.  Enabling duplicate, will
 result in psim creating a duplicate of the instruction's function for
@@ -343,7 +343,7 @@ disabled (using: --disable-sim-duplicate).
 Include/exclude PowerPC instructions that are specific to a particular
 implementation.
 
-Some of the PowerPC instructions included in the file ppc-instructions
+Some of the PowerPC instructions included in the file powerpc.igen
 are limited to certain specific PPC implementations.  For instance,
 the instruction:
 
diff --git a/sim/ppc/Makefile.in b/sim/ppc/Makefile.in
index 05f357a31a0..54e755e5bfe 100644
--- a/sim/ppc/Makefile.in
+++ b/sim/ppc/Makefile.in
@@ -607,10 +607,10 @@ tmp-dgen: dgen ppc-spr-table $(srcroot)/move-if-change
 	$(SILENCE) $(SHELL) $(srcroot)/move-if-change tmp-spreg.c spreg.c
 	$(SILENCE) touch $@
 
-tmp-igen: igen $(srcdir)/ppc-instructions $(srcdir)/altivec.igen $(srcdir)/e500.igen $(IGEN_OPCODE_RULES) $(srcroot)/move-if-change
+tmp-igen: igen $(srcdir)/powerpc.igen $(srcdir)/altivec.igen $(srcdir)/e500.igen $(IGEN_OPCODE_RULES) $(srcroot)/move-if-change
 	$(ECHO_GEN) $(IGEN) $(IGEN_FLAGS) \
 		-o $(srcdir)/$(IGEN_OPCODE_RULES) \
-		-I $(srcdir) -i $(srcdir)/ppc-instructions \
+		-I $(srcdir) -i $(srcdir)/powerpc.igen \
 		-n icache.h    -hc tmp-icache.h \
 		-n icache.c    -c  tmp-icache.c \
 		-n semantics.h -hs tmp-semantics.h \
diff --git a/sim/ppc/ppc-instructions b/sim/ppc/powerpc.igen
similarity index 100%
rename from sim/ppc/ppc-instructions
rename to sim/ppc/powerpc.igen

                 reply	other threads:[~2022-11-10 18:39 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=20221110183918.E8C7D3858D3C@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).