From nobody Thu Jun 20 11:04:40 2024 X-Original-To: freebsd-arch@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 4W4d1j6l3fz5NYZY for ; Thu, 20 Jun 2024 11:05:13 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W4d1j2yMGz4FqT for ; Thu, 20 Jun 2024 11:05:13 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1718881499; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wvOgMppuCDI8G+1/Fimflv3dc4W5D99rWWquhJlITPU=; b=kB6bgrcmsK5jmAg9GzdTRbNih3l9j0wHrHrqRy2dsZhpVT0pEVR65hgxjXkhYtYfiykjU/ ZswMITueL34s8GfMpd/2DwMJLSnhZcN3f0vckunHmO8hVZyH7joBBjQAuyZUhXjRLFalTf 7OdMPj9QWXgIr6W/Ei//0YlGzLLoWAjT4Z512eaJvrzhihgCFaY3Do+fnQ6ZmY/K+0ygu8 VCpzT/f/aPzRkJJnYNbjoFXvmrNW/97kZunG37QL0bConaRbEUPO724rjGDlfGKsod81T5 AwrdR2tE1FhhrdHmdWFW39pQh1xx0Tpi1hRtR4a2SZjMh1aK+3MF2ph6v8tg4w== Date: Thu, 20 Jun 2024 13:04:40 +0200 From: Alexander Leidinger To: Warner Losh Cc: freebsd-arch@freebsd.org Subject: Re: Minimum gcc and clang supported to generate FreeBSD binaries In-Reply-To: References: Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_cce6ace39ac330f11263c8a2aa52701f"; micalg=pgp-sha256 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:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4W4d1j2yMGz4FqT This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_cce6ace39ac330f11263c8a2aa52701f Content-Type: multipart/alternative; boundary="=_6155a0bc27e900ceb9f51cccbb5fb973" --=_6155a0bc27e900ceb9f51cccbb5fb973 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-06-20 03:01, schrieb Warner Losh: > ICC used to be supported, but unless someone turns up with patches for > the latest icc, it will remain supported only to the extent it pretends > to be gcc. I've had reports that it works, to this extent and nothing > special is needed to build FreeBSD binaries. There are a couple of > touch ups required to build FreeBSD itself with icc I'm told, but I've > not seen patches and have little desire to chase this windmill. As the one who introduced the ICC parts into cdefs.h: no objections from my side. This gained not as much traction than I thought it could have gotten. I'm not aware that apart from a handful of enthusiasts someone had a look at it. I'm surprised that someone still looks into compiling FreeBSD with icc, and that you have reports about it. We don't have a port of any recent icc (we could probably set an expiration date on the old ones). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_6155a0bc27e900ceb9f51cccbb5fb973 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Am 2024-06-20 03:01, schrieb Warner Losh:

 
ICC used to be supported, but unless someone turns up with patches for= the latest icc, it will remain supported only to the extent it pretends to= be gcc. I've had reports that it works, to this extent and nothing special= is needed to build FreeBSD binaries. There are a couple of touch ups requi= red to build FreeBSD itself with icc I'm told, but I've not seen patches an= d have little desire to chase this windmill.
 

As the one who introduced the ICC parts into cdefs.h: no objections from= my side. This gained not as much traction than I thought it could have got= ten. I'm not aware that apart from a handful of enthusiasts someone had a l= ook at it.

I'm surprised that someone still looks into compiling FreeBSD with icc, = and that you have reports about it. We don't have a port of any recent icc = (we could probably set an expiration date on the old ones).

Bye,
Alexander.

--
= http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http:/= /www.FreeBSD.org    n= etchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF
--=_6155a0bc27e900ceb9f51cccbb5fb973-- --=_cce6ace39ac330f11263c8a2aa52701f Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmZ0DNcACgkQEg2wmwP4 2IZ+ZhAAnp3wSeBgRHYNpjgo7bBpaK4Hm2NLjVjKyI8zAMHUKyRiNZTfkGY8OC0Y AazaV4VwYF9eUgwuI1ot4C4x2ilKAguZjBGoONVOIGxwgfG/33l9fLdqEEVugO+C Z0TrxeMIYtSZtvLytTyshrsP9k8Pqp5BaUq0Nlf0QaQLhp8N6K8UvM9yMGT1dmYa GrhzJ4Ce4mSLhUlZZ532Xnq8WAz4kVwPErKb8tXhn0V3JWmX+1MsVkNKL59Cvigs aYXrGQwSHo60MZZUCzoyyLbYsIqliDFZvFo1jn18TdNZd1Jg0TsJetbFqo0h7p4k f8apqT6Oni459DOkrGhRh0R0voeiBfTxo5V08Dbyi82ZpUqm6j2spCDNAQAEYfDI R9F+aot2rEEc1ebxh90EZ8x5DPU0SRSAccvVXv63Y6AU07Sy83cYzMWRXSUo1L1i 997Qh3UT7RiUZWgIOSqu6wIjsxzRchPvJkIi2YnvWZ2D+mdJqEyXsTNER5CoRbjg 7keMFUtKxqlHxdNgTuMtJ0erK/qfWrJFjS46FATsVy+4UwxMn1KKbnsyNfKy2+Ql MM74W8V3pSK8hLLuh/c7diACkrGx3QdLDLGxB95clC2A1lvU1WO32VzOyyvn14Ta I/w/U4LAe5PySGDJ/4FfENTi5t/x2FMp5iAclAOwC4bCBsfSI5o= =FWvU -----END PGP SIGNATURE----- --=_cce6ace39ac330f11263c8a2aa52701f--