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 (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 01AD8158008 for ; Thu, 15 Jun 2023 11:39:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 78DC4E08C3; Thu, 15 Jun 2023 11:39:50 +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)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 408F2E08AD for ; Thu, 15 Jun 2023 11:39:50 +0000 (UTC) References: User-agent: mu4e 1.10.3; emacs 29.0.91 From: Sam James To: gentoo-dev@lists.gentoo.org Cc: toolchain@gentoo.org Subject: Re: [gentoo-dev] What happened to gcc-12.3.0? Date: Thu, 15 Jun 2023 12:37:45 +0100 In-reply-to: Message-ID: <87bkhhhs3i.fsf@gentoo.org> 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 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: 166a6300-b803-4142-bea8-937e9fb15e50 X-Archives-Hash: 8ce9bdcae682126bcdd564ec06238493 --=-=-= Content-Type: text/plain Joshua Kinard writes: > Noticing that the ebuild for gcc-12.3.0 got dropped with little > explanation. It is the upstream stable release. I am eyeballing > #906310 as what may have triggered the drop, but I find it a bit of a > stretch that an upstream stable release got dropped over a single, > optional package that has a history of quirky behavior (FWIW, I never > had luck with ccache, especially on MIPS). Please see https://bugs.gentoo.org/908258. There were miscompilations even fixed after 12.3.0 was tagged. (Also, ccache really isn't a "package with quirky behaviour" in terms of whether or not it causes gcc to ICE. It has nothing to do with what ccache itself does at runtime.) >> > Under qemu, it takes about 4 hours to build the single-ABI variant of > gcc and 7 hours for the multilib variant. So I avoid rebuilding the > compiler as much as possible, as with six chroots, that's virtually an > entire day across all six just for gcc, minus distractions (seriously, > the build times on gcc are getting waaaaaaay out of hand, regardless > of arch). It should get a bit better as of recent 13 as we backported a change to help parallel builds at least (and reduce resource consumption). (Also, added toolchain@ to CC...) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZIr4gV8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZAEQAEArZK+22+ElcRv+qlQCaBomXky+L4kZNCfFdlo JUTY06cA+QFab0wU4ZzFzI1ynJXo7XkjKJtO8F/Q9kUO0eIT1QsP =/zup -----END PGP SIGNATURE----- --=-=-=--