public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5115] config-list.mk: Remove obsolete FreeBSD targets
Date: Thu, 12 Jan 2023 00:09:07 +0000 (GMT) [thread overview]
Message-ID: <20230112000907.0B1AD3858D35@sourceware.org> (raw)
https://gcc.gnu.org/g:306ff653a3a542bcb930c8d25e178677faa2246a
commit r13-5115-g306ff653a3a542bcb930c8d25e178677faa2246a
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Thu Jan 12 01:00:40 2023 +0100
config-list.mk: Remove obsolete FreeBSD targets
ia64-freebsd is officially dead, and sparc64-freebsd has not been able
to build GCC for half a dozen years (or so) and is essentially end of
life.
The default per gcc/config/i386/freebsd.h has been i586 for a while,
so i486-freebsd can go as well. (We still have i686-freebsd.)
contrib/ChangeLog:
* config-list.mk: Remove i486-freebsd4, ia64-freebsd6, and
sparc64-freebsd6.
Diff:
---
contrib/config-list.mk | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/contrib/config-list.mk b/contrib/config-list.mk
index 2056a221ac2..05184eaa701 100644
--- a/contrib/config-list.mk
+++ b/contrib/config-list.mk
@@ -48,14 +48,14 @@ LIST = aarch64-elf aarch64-linux-gnu aarch64-rtems \
hppa64-hpux11.3 \
hppa64-hpux11.0OPT-enable-sjlj-exceptions=yes \
i686-pc-linux-gnu i686-apple-darwin i686-apple-darwin9 i686-apple-darwin10 \
- i486-freebsd4 i686-freebsd6 i686-kfreebsd-gnu \
+ i686-freebsd6 i686-kfreebsd-gnu \
i686-netbsdelf9 \
i686-openbsd i686-elf i686-kopensolaris-gnu i686-symbolics-gnu \
i686-pc-msdosdjgpp i686-lynxos i686-nto-qnx \
i686-rtems i686-solaris2.11 i686-wrs-vxworks \
i686-wrs-vxworksae \
i686-cygwinOPT-enable-threads=yes i686-mingw32crt ia64-elf \
- ia64-freebsd6 ia64-linux ia64-hpux ia64-hp-vms iq2000-elf lm32-elf \
+ ia64-linux ia64-hpux ia64-hp-vms iq2000-elf lm32-elf \
lm32-rtems lm32-uclinux \
loongarch64-linux-gnuf64 loongarch64-linux-gnuf32 loongarch64-linux-gnusf \
m32c-elf m32r-elf m32rle-elf \
@@ -93,7 +93,7 @@ LIST = aarch64-elf aarch64-linux-gnu aarch64-rtems \
sparc-leon-elf sparc-rtems sparc-linux-gnu \
sparc-leon3-linux-gnuOPT-enable-target=all sparc-netbsdelf \
sparc64-sun-solaris2.11OPT-with-gnu-ldOPT-with-gnu-asOPT-enable-threads=posix \
- sparc-wrs-vxworks sparc64-elf sparc64-rtems sparc64-linux sparc64-freebsd6 \
+ sparc-wrs-vxworks sparc64-elf sparc64-rtems sparc64-linux \
sparc64-netbsd sparc64-openbsd \
v850e1-elf v850e-elf v850-elf v850-rtems vax-linux-gnu \
vax-netbsdelf visium-elf x86_64-apple-darwin \
reply other threads:[~2023-01-12 0:09 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=20230112000907.0B1AD3858D35@sourceware.org \
--to=gerald@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.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).