From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (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) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A6834158232 for ; Sun, 8 Dec 2024 13:02:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 08D3CE0C68; Sun, 8 Dec 2024 13:02:12 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 50294E0C5E for ; Sun, 8 Dec 2024 13:02:11 +0000 (UTC) Message-ID: <8057d12150fa55106e1d5568426c46741efb1295.camel@gentoo.org> Subject: Re: [gentoo-dev] [RFC] New categories for LLVM From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Sun, 08 Dec 2024 14:02:06 +0100 In-Reply-To: <87ikrux19a.fsf@gentoo.org> References: <87f27044c599b4168d27d79367fd4b47575502c9.camel@gentoo.org> <87ikrux19a.fsf@gentoo.org> Organization: Gentoo Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-8RXcPvm28JXHwGDTusyh" User-Agent: Evolution 3.52.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 X-Archives-Salt: e2ff9407-5152-435d-8b4f-44f08276a105 X-Archives-Hash: 830d93b9fa66bf0183046a25afd904f9 --=-8RXcPvm28JXHwGDTusyh Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, 2024-12-08 at 04:11 +0000, Sam James wrote: > I'm not sure if I'm sold on *two*. What happens for stuff like mlir > where it's not a runtime but it's arguably more of one than core? >=20 > It just doesn't feel like the division works great. Or maybe it's just > because I feel like llvm-core will keep growing and llvm-runtimes won't. Well, upstream has a split between "projects" and "runtimes", and I think it makes sense to follow that. "compiler-rt" and "libc" happen to be listed in both, but I suppose it's more of a historical thing -- I think you're always supposed to be doing the runtimes build for projects that support it these days. Right now, we don't package libc, pstl, llvm-libgcc -- so there are definitely more potential packages to be added. I suspect that this split will also help with crossdev. FWIU we only need to cover runtimes there, since the toolchain itself is cross- capable by design. --=20 Best regards, Micha=C5=82 G=C3=B3rny --=-8RXcPvm28JXHwGDTusyh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFGBAABCgAwFiEEx2qEUJQJjSjMiybFY5ra4jKeJA4FAmdVmM4SHG1nb3JueUBn ZW50b28ub3JnAAoJEGOa2uIyniQOEdEH/jhN3iVPyZgfbzTWFcd9vnRm1mftStQD JMdDk4OwEHBJ7HmhFMqeqrhSZ9RvAHnCJ3Y0yUBDcu6mgiRtfmqmMmghajumvCBn q4LPTUHOC0RIk1jM6o7OlL33SFUy6Fxcxl3J1VhudQBvc07LuLhRAbhEJOMCrdbV NsrwvnlAOrXkxcuxFFYu0WCRsaligIUotclS9qoITh9S6mQyICQFyltxPX2Sz15Z ++vc4CdIUA77QA/hjYQFiKK+ItA15t7QfVmu3gQGLZozRAZDSv8BJdTT7QqQOC5w ekU1xANFsVrQAjD0Qryd/+bGio/2lFYlEN63tZnJIAsRKMTwaLFlQLk= =Bpul -----END PGP SIGNATURE----- --=-8RXcPvm28JXHwGDTusyh--