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: m32r: fix typos in stamp depends
Date: Sun, 15 Jan 2023 07:10:35 +0000 (GMT)	[thread overview]
Message-ID: <20230115071035.DEF423858C78@sourceware.org> (raw)

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

commit 2025c82b95427f839e20c7c9b861c84bf5c72113
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Sun Jan 15 02:05:06 2023 -0500

    sim: m32r: fix typos in stamp depends
    
    Copying & pasting the first rule missed updating the dep to the right
    stamp file.

Diff:
---
 sim/Makefile.in   | 4 ++--
 sim/m32r/local.mk | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/sim/Makefile.in b/sim/Makefile.in
index 3f8713339b4..57abd19b7c8 100644
--- a/sim/Makefile.in
+++ b/sim/Makefile.in
@@ -5293,7 +5293,7 @@ testsuite/common/bits64m63.c: testsuite/common/bits-gen$(EXEEXT) testsuite/commo
 @SIM_ENABLE_ARCH_m32r_TRUE@	$(AM_V_at)$(SHELL) $(srcroot)/move-if-change m32r/mloop.cin m32r/mloop.c
 @SIM_ENABLE_ARCH_m32r_TRUE@	$(AM_V_at)touch $@
 
-@SIM_ENABLE_ARCH_m32r_TRUE@m32r/mloopx.c m32r/engx.h: m32r/stamp-mloop ; @true
+@SIM_ENABLE_ARCH_m32r_TRUE@m32r/mloopx.c m32r/engx.h: m32r/stamp-mloop-x ; @true
 @SIM_ENABLE_ARCH_m32r_TRUE@m32r/stamp-mloop-x: $(srccom)/genmloop.sh m32r/mloop.in
 @SIM_ENABLE_ARCH_m32r_TRUE@	$(AM_V_GEN)$(SHELL) $(srccom)/genmloop.sh -shell $(SHELL) \
 @SIM_ENABLE_ARCH_m32r_TRUE@		-mono -no-fast -pbb -parallel-write -switch semx-switch.c \
@@ -5303,7 +5303,7 @@ testsuite/common/bits64m63.c: testsuite/common/bits-gen$(EXEEXT) testsuite/commo
 @SIM_ENABLE_ARCH_m32r_TRUE@	$(AM_V_at)$(SHELL) $(srcroot)/move-if-change m32r/mloopx.cin m32r/mloopx.c
 @SIM_ENABLE_ARCH_m32r_TRUE@	$(AM_V_at)touch $@
 
-@SIM_ENABLE_ARCH_m32r_TRUE@m32r/mloop2.c m32r/eng2.h: m32r/stamp-mloop ; @true
+@SIM_ENABLE_ARCH_m32r_TRUE@m32r/mloop2.c m32r/eng2.h: m32r/stamp-mloop-2 ; @true
 @SIM_ENABLE_ARCH_m32r_TRUE@m32r/stamp-mloop-2: $(srccom)/genmloop.sh m32r/mloop.in
 @SIM_ENABLE_ARCH_m32r_TRUE@	$(AM_V_GEN)$(SHELL) $(srccom)/genmloop.sh -shell $(SHELL) \
 @SIM_ENABLE_ARCH_m32r_TRUE@		-mono -no-fast -pbb -parallel-write -switch sem2-switch.c \
diff --git a/sim/m32r/local.mk b/sim/m32r/local.mk
index 85190650e8e..072618ff93f 100644
--- a/sim/m32r/local.mk
+++ b/sim/m32r/local.mk
@@ -112,7 +112,7 @@ BUILT_SOURCES += \
 	$(AM_V_at)touch $@
 
 ## FIXME: Use of `mono' is wip.
-%D%/mloopx.c %D%/engx.h: %D%/stamp-mloop ; @true
+%D%/mloopx.c %D%/engx.h: %D%/stamp-mloop-x ; @true
 %D%/stamp-mloop-x: $(srccom)/genmloop.sh %D%/mloop.in
 	$(AM_V_GEN)$(SHELL) $(srccom)/genmloop.sh -shell $(SHELL) \
 		-mono -no-fast -pbb -parallel-write -switch semx-switch.c \
@@ -123,7 +123,7 @@ BUILT_SOURCES += \
 	$(AM_V_at)touch $@
 
 ## FIXME: Use of `mono' is wip.
-%D%/mloop2.c %D%/eng2.h: %D%/stamp-mloop ; @true
+%D%/mloop2.c %D%/eng2.h: %D%/stamp-mloop-2 ; @true
 %D%/stamp-mloop-2: $(srccom)/genmloop.sh %D%/mloop.in
 	$(AM_V_GEN)$(SHELL) $(srccom)/genmloop.sh -shell $(SHELL) \
 		-mono -no-fast -pbb -parallel-write -switch sem2-switch.c \

                 reply	other threads:[~2023-01-15  7:10 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=20230115071035.DEF423858C78@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).