From nobody Tue Feb 6 16:35:30 2024 X-Original-To: freebsd-toolchain@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TTpl64Smkz59YmZ; Tue, 6 Feb 2024 16:35:30 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TTpl643qdz3wtB; Tue, 6 Feb 2024 16:35:30 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 2CDC33C019A; Tue, 6 Feb 2024 16:35:30 +0000 (UTC) Date: Tue, 6 Feb 2024 16:35:30 +0000 From: Brooks Davis To: Mark Millard Cc: FreeBSD Toolchain , FreeBSD Mailing List Subject: Re: Why does Mk/Uses/compiler.mk have code for "# clang not always supported on Tier-2" these days? Message-ID: References: List-Id: Maintenance of FreeBSD s integrated toolchain List-Archive: https://lists.freebsd.org/archives/freebsd-toolchain List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4TTpl643qdz3wtB X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US] On Tue, Feb 06, 2024 at 02:34:14AM -0800, Mark Millard wrote: > Mk/Uses/compiler.mk has the .if test : > > if (defined(FAVORITE_COMPILER) && ${FAVORITE_COMPILER} == gcc) || (${ARCH} != amd64 && ${ARCH} != i386) # clang not always supported on Tier-2 > > Should it instead allow clang generally these days via > instead being: > > if (defined(FAVORITE_COMPILER) && ${FAVORITE_COMPILER} == gcc) Indeed, I'd noticed this a while back and then forgot about it after patching it out in CheriBSD-ports. It's utter nonsense. > Would this need some sort of exp-run sequence? If we have the capacity to do an aarch64 run then that might be useful. Otherwise the appropriate person should probably just commit it and deal with the fallout. -- Brooks