public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6269] In 'contrib/config-list.mk', clarify i686-symbolics-gnu to i686-gnu
Date: Wed, 22 Feb 2023 08:11:13 +0000 (GMT)	[thread overview]
Message-ID: <20230222081113.89BDC3858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:10f085135bc98afa57309fcd679698a0122925bf

commit r13-6269-g10f085135bc98afa57309fcd679698a0122925bf
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Fri Feb 10 10:43:24 2023 +0100

    In 'contrib/config-list.mk', clarify i686-symbolics-gnu to i686-gnu
    
    Already in the first revision of 'contrib/config-list.mk', i686-symbolics-gnu
    has been present, but it's not clear to me whether that was meant to be
    Symbolics as in the manufacturer, <https://en.wikipedia.org/wiki/Symbolics>,
    with GNU (that is, GNU/Hurd) kernel/operating system (user land), or Symbolics
    kernel with GNU operating system (user land)?
    
    I can't find any mention of "Symbolics" in the history of 'config.sub'
    upstream.
    
    Either way, GCC configures i686-symbolics-gnu exactly the same as i686-gnu:
    
        $ sed -n -e '/Using .* host machine hooks\.$/q' -e '/^Using the following target machine macro files:$/,$p' log/i686-gnu-make.out
        Using the following target machine macro files:
                [...]/gcc/config/vxworks-dummy.h
                [...]/gcc/config/i386/i386.h
                [...]/gcc/config/i386/unix.h
                [...]/gcc/config/i386/att.h
                [...]/gcc/config/elfos.h
                [...]/gcc/config/gnu-user.h
                [...]/gcc/config/glibc-stdint.h
                [...]/gcc/config/i386/gnu-user-common.h
                [...]/gcc/config/i386/gnu-user.h
                [...]/gcc/config/gnu.h
                [...]/gcc/config/i386/gnu.h
                [...]/gcc/config/initfini-array.h
    
    ..., so let's clarify i686-symbolics-gnu to i686-gnu.
    
            contrib/
            * config-list.mk (LIST): Clarify i686-symbolics-gnu to i686-gnu.

Diff:
---
 contrib/config-list.mk | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/config-list.mk b/contrib/config-list.mk
index 661b11c9bbd..e570b13c71b 100644
--- a/contrib/config-list.mk
+++ b/contrib/config-list.mk
@@ -50,7 +50,7 @@ LIST = aarch64-elf aarch64-freebsd13 aarch64-linux-gnu aarch64-rtems \
   i686-pc-linux-gnu i686-apple-darwin i686-apple-darwin9 i686-apple-darwin10 \
   i686-freebsd13 i686-kfreebsd-gnu \
   i686-netbsdelf9 \
-  i686-openbsd i686-elf i686-kopensolaris-gnu i686-symbolics-gnu \
+  i686-openbsd i686-elf i686-kopensolaris-gnu i686-gnu \
   i686-pc-msdosdjgpp i686-lynxos i686-nto-qnx \
   i686-rtems i686-solaris2.11 i686-wrs-vxworks \
   i686-wrs-vxworksae \

                 reply	other threads:[~2023-02-22  8:11 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=20230222081113.89BDC3858D3C@sourceware.org \
    --to=tschwinge@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).