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: m32c/rx: drop useless $(ENDLIST)
Date: Thu,  3 Nov 2022 18:39:52 +0000 (GMT)	[thread overview]
Message-ID: <20221103183952.6BFC53858412@sourceware.org> (raw)

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

commit 8183b5f53f7a2d50085f6584d1bd846aff6b5dbf
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Fri Nov 4 01:07:53 2022 +0700

    sim: m32c/rx: drop useless $(ENDLIST)
    
    This is used to allow for dangling \ in object lists, but these are the
    only ports that do it, and it isn't really necessary.  Punt it to keep
    the various makefiles harmonized.

Diff:
---
 sim/m32c/Makefile.in | 7 ++-----
 sim/rx/Makefile.in   | 7 ++-----
 2 files changed, 4 insertions(+), 10 deletions(-)

diff --git a/sim/m32c/Makefile.in b/sim/m32c/Makefile.in
index 2436eb940f4..ea4320540a9 100644
--- a/sim/m32c/Makefile.in
+++ b/sim/m32c/Makefile.in
@@ -22,9 +22,7 @@
 
 SIM_EXTRA_CFLAGS = -DTIMER_A
 
-SIM_RUN_OBJS = \
-	main.o \
-	$(ENDLIST)
+SIM_RUN_OBJS = main.o
 
 SIM_OBJS = \
 	gdb-if.o \
@@ -37,7 +35,6 @@ SIM_OBJS = \
 	m32c.o \
 	srcdest.o \
 	syscalls.o \
-	trace.o \
-	$(ENDLIST)
+	trace.o
 
 ## COMMON_POST_CONFIG_FRAG
diff --git a/sim/rx/Makefile.in b/sim/rx/Makefile.in
index c845fceb2fc..4e1f2acf214 100644
--- a/sim/rx/Makefile.in
+++ b/sim/rx/Makefile.in
@@ -22,9 +22,7 @@
 
 SIM_EXTRA_CFLAGS = @SIM_RX_CYCLE_ACCURATE_FLAGS@
 
-SIM_RUN_OBJS = \
-	main.o \
-	$(ENDLIST)
+SIM_RUN_OBJS = main.o
 
 SIM_OBJS = \
 	fpu.o \
@@ -36,8 +34,7 @@ SIM_OBJS = \
 	syscalls.o \
 	trace.o \
 	gdb-if.o \
-	err.o \
-	$(ENDLIST)
+	err.o
 
 ## COMMON_POST_CONFIG_FRAG

                 reply	other threads:[~2022-11-03 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=20221103183952.6BFC53858412@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).