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 775E3158008 for ; Thu, 15 Jun 2023 04:02:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BBBF4E092F; Thu, 15 Jun 2023 04:02:18 +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 57846E08BE for ; Thu, 15 Jun 2023 04:02:17 +0000 (UTC) Message-ID: Date: Thu, 15 Jun 2023 00:02:14 -0400 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/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.11.0 Content-Language: en-US To: gentoo-dev@lists.gentoo.org From: Joshua Kinard Subject: [gentoo-dev] What happened to gcc-12.3.0? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 0bb97a17-f79a-4949-ba2c-fa43b1b62e60 X-Archives-Hash: 9ccbdf093fe1c6809c4258096a46d159 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). I know we have the pYYYMMDD ebuilds, but I've been keeping my mips chroots on only the upstream/stable releases to minimize the number of times I have to rebuild the compiler, since we make frequent pYYYYMMDD releases (once a month, on average, judging by the datestamps), and most of the patches in the pYYYYMMDD series don't help or hinder MIPS. 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). Options? I mean, if anyone knows magic to make gcc build faster, I am all ears, but ever since the switch to C++, the time needed for it to build itself has just been absolutely horrendous. And it gets worse with each new release, for some reason. -- Joshua Kinard Gentoo/MIPS kumba@gentoo.org rsa6144/5C63F4E3F5C6C943 2015-04-27 177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic