public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin/users/vapier/wip] libgloss: i960: delete dead/broken code Date: Tue, 2 Jan 2024 04:36:05 +0000 (GMT) [thread overview] Message-ID: <20240102043605.BF6413858C2C@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=79ae6461b88b04337922ca5cf054ec3b83558956 commit 79ae6461b88b04337922ca5cf054ec3b83558956 Author: Mike Frysinger <vapier@gentoo.org> Date: Tue Dec 26 20:53:43 2023 -0500 libgloss: i960: delete dead/broken code The i960 port has a lot of references to sim files that have never been included in the tree afaict, and thus has never worked. Delete all the code to simplify. Diff: --- libgloss/i960/Makefile.in | 37 ------------------------------------- 1 file changed, 37 deletions(-) diff --git a/libgloss/i960/Makefile.in b/libgloss/i960/Makefile.in index bf1a49e58..0d1b80029 100644 --- a/libgloss/i960/Makefile.in +++ b/libgloss/i960/Makefile.in @@ -49,22 +49,12 @@ OBJS = putnum.o unlink.o CFLAGS = -g SCRIPTS = -# Here is all of the simulator stuff -SIM_SCRIPTS = -SIM_LDFLAGS = -SIM_BSP = libsim.a -SIM_CRT0 = sim-crt0.o -SIM_OBJS = sim-print.o sim-inbyte.o sim-sbrk.o sim-abort.o sim-errno.o simulator.o -SIM_TEST = sim-test -SIM_INSTALL = install-sim - # Here is all of the mon960 stuff MON_LDFLAGS = MON_BSP = libmon960.a MON_CRT0 = crt0.o MON_OBJS = mon-read.o mon-write.o mon-syscalls.o mon960.o MON_SCRIPTS = mon960.ld -MON_TEST = MON_INSTALL = install-mon # Host specific makefile fragment comes in here. @@ -79,39 +69,16 @@ all: ${MON_CRT0} ${MON_BSP} # # here's where we build the board support packages for each target # -${SIM_BSP}: ${OBJS} ${SIM_OBJS} - ${AR} ${ARFLAGS} ${SIM_BSP} ${SIM_OBJS} ${OBJS} - ${RANLIB} ${SIM_BSP} - ${MON_BSP}: ${OBJS} ${MON_OBJS} ${AR} ${ARFLAGS} ${MON_BSP} ${MON_OBJS} ${OBJS} ${RANLIB} ${MON_BSP} -# -# here's where we build the test programs for each target -# -.PHONY: test -test: ${SIM_TEST} ${MVME_TEST} ${EVM_TEST} - -sim-test: sim-test.x sim-test.dis - -sim-test.x: test.o ${SIM_CRT0} ${SIM_BSP} - ${CC} ${LDFLAGS_FOR_TARGET} -L${objdir} \ - ${SIM_CRT0} test.o \ - -o sim-test.x ${LIBS_FOR_TARGET} -lc ${SIM_BSP} - -sim-test.dis: sim-test.x - ${OBJDUMP} -d sim-test.x > sim-test.dis - - # # # .c.S: ${CC} ${CFLAGS_FOR_TARGET} -c $< -simulator.o: simulator.S -sim-crt0.o: sim-crt0.S mvme-crt0.o: mvme-crt0.S mvme-exit.o: mvme-exit.S mvme-inbyte.o: mvme-inbyte.S @@ -131,10 +98,6 @@ install-mon: set -e; for x in ${MON_CRT0} ${MON_BSP}; do ${INSTALL_DATA} $$x $(DESTDIR)${tooldir}/lib${MULTISUBDIR}/$$x; done set -e; for x in ${MON_SCRIPTS}; do ${INSTALL_DATA} ${srcdir}/$$x $(DESTDIR)${tooldir}/lib${MULTISUBDIR}/$$x; done -install-sim: - ${mkinstalldirs} ${DESTDIR}${tooldir}/lib - set -e; for x in ${SIM_CRT0} ${SIM_BSP} ${SIM_SCRIPTS}; do ${INSTALL_DATA} $$x $(DESTDIR)${tooldir}/lib/$$x; done - doc: info: install-info:
reply other threads:[~2024-01-02 4:36 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=20240102043605.BF6413858C2C@sourceware.org \ --to=vapier@sourceware.org \ --cc=newlib-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: linkBe 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).