public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 8/9] sim: or1k: hoist cgen rules to top-level
Date: Sun,  1 Jan 2023 23:32:08 -0500	[thread overview]
Message-ID: <20230102043209.21542-8-vapier@gentoo.org> (raw)
In-Reply-To: <20230102043209.21542-1-vapier@gentoo.org>

---
 sim/Makefile.in      |  8 ++++++++
 sim/or1k/Makefile.in | 34 ----------------------------------
 sim/or1k/local.mk    |  8 ++++++++
 3 files changed, 16 insertions(+), 34 deletions(-)

diff --git a/sim/or1k/Makefile.in b/sim/or1k/Makefile.in
index 6b2a976d8aef..ca5bf1ae4eee 100644
--- a/sim/or1k/Makefile.in
+++ b/sim/or1k/Makefile.in
@@ -45,37 +45,3 @@ SIM_EXTRA_CFLAGS = -DWITH_TARGET_WORD_BITSIZE=32 -DWITH_TARGET_WORD_MSB=31
 ## COMMON_POST_CONFIG_FRAG
 
 arch = or1k
-
-stamps: stamp-arch stamp-cpu
-
-# NOTE: Generated source files are specified as full paths,
-# e.g. $(srcdir)/arch.c, because make may decide the files live
-# in objdir otherwise.
-
-OR1K_CGEN_DEPS = \
-	$(CPU_DIR)/or1k.cpu \
-	$(CPU_DIR)/or1k.opc \
-	$(CPU_DIR)/or1kcommon.cpu \
-	$(CPU_DIR)/or1korbis.cpu \
-	$(CPU_DIR)/or1korfpx.cpu \
-	Makefile
-
-stamp-arch: $(CGEN_READ_SCM) $(CGEN_ARCH_SCM) $(OR1K_CGEN_DEPS)
-	$(MAKE) cgen-arch $(CGEN_FLAGS_TO_PASS) \
-	  mach=or32,or32nd \
-	  archfile=$(CPU_DIR)/or1k.cpu \
-	  FLAGS="with-scache"
-	$(SILENCE) touch $@
-$(srcdir)/arch.h $(srcdir)/arch.c $(srcdir)/cpuall.h: $(CGEN_MAINT) stamp-arch
-	@true
-
-stamp-cpu: $(CGEN_READ_SCM) $(CGEN_CPU_SCM) $(OR1K_CGEN_DEPS)
-	$(MAKE) cgen-cpu-decode $(CGEN_FLAGS_TO_PASS) \
-	  cpu=or1k32bf \
-	  mach=or32,or32nd \
-	  archfile=$(CPU_DIR)/or1k.cpu \
-	  FLAGS="with-scache" \
-	  EXTRAFILES="$(CGEN_CPU_SEM) $(CGEN_CPU_SEMSW)"
-	$(SILENCE) touch $@
-$(srcdir)/cpu.h $(srcdir)/cpu.c $(srcdir)/model.c $(srcdir)/sem.c $(srcdir)/sem-switch.c $(srcdir)/decode.c $(srcdir)/decode.h: $(CGEN_MAINT) stamp-cpu
-	@true
diff --git a/sim/or1k/local.mk b/sim/or1k/local.mk
index b332bfab59d6..1b5c44fa5edc 100644
--- a/sim/or1k/local.mk
+++ b/sim/or1k/local.mk
@@ -46,3 +46,11 @@ SIM_ALL_RECURSIVE_DEPS += $(%C%_BUILD_OUTPUTS)
 	$(AM_V_at)touch $@
 
 MOSTLYCLEANFILES += $(%C%_BUILD_OUTPUTS)
+
+%D%/cgen-arch:
+	$(AM_V_GEN)mach=or32,or32nd FLAGS="with-scache"; $(CGEN_GEN_ARCH)
+%D%/arch.h %D%/arch.c %D%/cpuall.h: @CGEN_MAINT@ %D%/cgen-arch
+
+%D%/cgen-cpu-decode:
+	$(AM_V_GEN)cpu=or1k32bf mach=or32,or32nd FLAGS="with-scache" EXTRAFILES="$(CGEN_CPU_SEM) $(CGEN_CPU_SEMSW)"; $(CGEN_GEN_CPU_DECODE)
+%D%/cpu.h %D%/cpu.c %D%/model.c %D%/sem.c %D%/sem-switch.c %D%/decode.c %D%/decode.h: @CGEN_MAINT@ %D%/cgen-cpu-decode
-- 
2.39.0


  parent reply	other threads:[~2023-01-02  4:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02  4:32 [PATCH 1/9] sim: cgen: hoist rules to the top-level build Mike Frysinger
2023-01-02  4:32 ` [PATCH 2/9] sim: bpf: hoist cgen rules to top-level Mike Frysinger
2023-01-02  4:32 ` [PATCH 3/9] sim: cris: " Mike Frysinger
2023-01-02  4:32 ` [PATCH 4/9] sim: frv: " Mike Frysinger
2023-01-02  4:32 ` [PATCH 5/9] sim: iq2000: " Mike Frysinger
2023-01-02  4:32 ` [PATCH 6/9] sim: lm32: " Mike Frysinger
2023-01-02  4:32 ` [PATCH 7/9] sim: m32r: " Mike Frysinger
2023-01-02  4:32 ` Mike Frysinger [this message]
2023-01-02  4:32 ` [PATCH 9/9] sim: cgen: drop common subdir build rules Mike Frysinger

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=20230102043209.21542-8-vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@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).