From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96355 invoked by alias); 4 Mar 2017 16:40:35 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 96326 invoked by uid 89); 4 Mar 2017 16:40:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-26.9 required=5.0 tests=BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*Ad:U*andreast, marketing X-Spam-User: qpsmtpd, 2 recipients X-HELO: ainaz.pair.com Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 04 Mar 2017 16:40:33 +0000 Received: from anthias (vie-188-118-249-200.dsl.sil.at [188.118.249.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 0E8013F5D6; Sat, 4 Mar 2017 11:40:28 -0500 (EST) Date: Sat, 04 Mar 2017 16:40:00 -0000 From: Gerald Pfeifer To: Richard Biener cc: Ramana Radhakrishnan , Andreas Tobler , gcc-patches@gcc.gnu.org Subject: i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) In-Reply-To: Message-ID: References: <5742CA86.10200@foss.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00209.txt.bz2 On Tue, 24 May 2016, Richard Biener wrote: >> As Jeff noted, i386 actually is the "marketing" name used for the >> platform, GCC has been defaulting to i486 for ages, and I upgraded >> to i586 last year: >> >> 2015-11-15 Gerald Pfeifer >> >> * config/i386/freebsd.h (SUBTARGET32_DEFAULT_CPU): Change to i586. >> Remove support for FreeBSD 5 and earlier. > Can we update to a non-marketing name then, like i586-unknown-freebsd please? > config.gcc accepts i[34567]86-*-freebsd*. It at least confused me. Sooo, I finally got to submitting the patch below to the config.guess maintainers. When/if this has been accepted, is it okay to pull the latest config.guess into GCC even at this stage of the release process? (We're only looking at this change and the addition of nsx-tandem compared to what we have right now.) Gerald 2017-03-04 Gerald Pfeifer * config.guess (*:FreeBSD:*:*): Refactor CPU handling. Canonicalize i386-*-freebsd* to i586-*-freebsd*. diff --git a/config.guess b/config.guess index 1000e2b..180375c 100755 --- a/config.guess +++ b/config.guess @@ -837,10 +837,11 @@ EOF UNAME_PROCESSOR=`/usr/bin/uname -p` case ${UNAME_PROCESSOR} in amd64) - echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;; - *) - echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;; + UNAME_PROCESSOR=x86_64 ;; + i386) + UNAME_PROCESSOR=i586 ;; esac + echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` exit ;; i*:CYGWIN*:*) echo ${UNAME_MACHINE}-pc-cygwin