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)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8290E158232 for ; Sun, 8 Dec 2024 22:23:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8BAFAE0D75; Sun, 8 Dec 2024 22:23:56 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (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 CCF39E0D36 for ; Sun, 8 Dec 2024 22:23:55 +0000 (UTC) Message-ID: <3d7fa48e-2b92-4669-98d7-36b243c263e4@gentoo.org> Date: Sun, 8 Dec 2024 17:23:51 -0500 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 User-Agent: Mozilla Thunderbird Subject: Re: [gentoo-dev] Re: LLVM build strategy To: gentoo-dev@lists.gentoo.org References: <87f27044c599b4168d27d79367fd4b47575502c9.camel@gentoo.org> <87a5d6wza1.fsf@gentoo.org> <579176956c4663fa4f13d09530fc87ea375a592f.camel@gentoo.org> <87bjxlvog1.fsf@gentoo.org> Content-Language: en-US From: Eli Schwartz Autocrypt: addr=eschwartz@gentoo.org; keydata= xjMEZmeRNBYJKwYBBAHaRw8BAQdAYNZ7pUDWhx1i2f3p6L2ZLu4FcY18UoeGC04Gq/khqwfN I0VsaSBTY2h3YXJ0eiA8ZXNjaHdhcnR6QGdlbnRvby5vcmc+wpYEExYKAD4WIQTvUdMIsc4j CIi+DYTqQj6ToWND8QUCZoRL+gIbAwUJBKKGAAULCQgHAwUVCgkICwUWAgMBAAIeBQIXgAAK CRDqQj6ToWND8aB5AP9r4kB691nNtNwKkdRiOdl7/k6WYzokvHvDamXxRJ0I+gEAjZqR5V8y mfR3fy2Z+r2Joeqdt3CIv5IwPs64spBvigLOOARmZ5E0EgorBgEEAZdVAQUBAQdATT46Z06b 1X9xjXFCYFxmq/Tj3tSEKZInDWTpoHQp4l8DAQgHwn4EGBYKACYWIQTvUdMIsc4jCIi+DYTq Qj6ToWND8QUCZmeRNAIbDAUJBKKGAAAKCRDqQj6ToWND8a2RAP40KPfbfoiZAJW5boFmFJ3G TUBDJRh9CWHyaPqq2PN+0wD/R07oLzfnJUN209mzi9TuTuHjeZybysyqXSw4MAxkMAY= In-Reply-To: <87bjxlvog1.fsf@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------W0qPi7WeacycQtY7sqdtplln" X-Archives-Salt: dbd2eca1-e830-4a1e-a6fe-4110c79aa1e0 X-Archives-Hash: 1650f7cac54f4a11203cbdffcd02a52b This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------W0qPi7WeacycQtY7sqdtplln Content-Type: multipart/mixed; boundary="------------jzVRs86tjz8H6gCbR6DNnKFE"; protected-headers="v1" From: Eli Schwartz To: gentoo-dev@lists.gentoo.org Message-ID: <3d7fa48e-2b92-4669-98d7-36b243c263e4@gentoo.org> Subject: Re: [gentoo-dev] Re: LLVM build strategy References: <87f27044c599b4168d27d79367fd4b47575502c9.camel@gentoo.org> <87a5d6wza1.fsf@gentoo.org> <579176956c4663fa4f13d09530fc87ea375a592f.camel@gentoo.org> <87bjxlvog1.fsf@gentoo.org> In-Reply-To: <87bjxlvog1.fsf@gentoo.org> --------------jzVRs86tjz8H6gCbR6DNnKFE Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/8/24 4:45 PM, Sam James wrote: >> I don't like the idea of spending hours building everything before I'm= >> even able to start running tests, just to learn that LLVM is broken >> and there's no point in even starting to build the rest. >=20 > I don't follow this bit -- you need the new LLVM merged before you can > build Clang's tests, right? And if any of it fails to build, it's not > like we can commit the release or snapshot? >=20 > What am I missing on this bit? I think the point here is that currently, one can build sys-devel/llvm with tests enabled, and if it fails, there's no point in also building sys-devel/clang. But with a monorepo build, you'd have to build llvm, clang (and various others) first, and then launch tests for llvm and clang together, only to get a test failure in the llvm tests that indicates everything else is broken too. Depending on cmake test ordering, you may also run half the clang tests before hitting the llvm failures, even. In theory this could be solved by building monorepo-llvm with FEATURES=3Dtest USE=3D"-clang" to start running tests, and then if that passes, rebuild llvm again but this time with clang etc. enabled. Not sure this is actually solving the stated objection... --=20 Eli Schwartz --------------jzVRs86tjz8H6gCbR6DNnKFE-- --------------W0qPi7WeacycQtY7sqdtplln Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature.asc" -----BEGIN PGP SIGNATURE----- wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZ1YcdwUDAAAAAAAKCRCEp9ErcA0vVw9e AP9M/jRJuKic1e+4FVCR5Oa+ddqk85LQLUMKLphL20iz8AEAobATqrf2DlA/i/UXjvWjU6LRAWLm FAI+Xo8uJvLueA4= =4wCR -----END PGP SIGNATURE----- --------------W0qPi7WeacycQtY7sqdtplln--