From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] What happened to gcc-12.3.0?
Date: Thu, 15 Jun 2023 11:47:55 -0400 [thread overview]
Message-ID: <e3b2b943-289a-e256-7c71-5b7cd32b2de7@gentoo.org> (raw)
In-Reply-To: <CAEdQ38GsL6Mk-TDoHDt9vquxsntcM-qo1orYt8b9pKxQkoFBpQ@mail.gmail.com>
On 6/15/2023 01:04, Matt Turner wrote:
> On Thu, Jun 15, 2023 at 12:02 AM Joshua Kinard <kumba@gentoo.org> wrote:
> 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.
>
> EXTRA_ECONF=--disable-bootstrap
>
> See https://bugs.gentoo.org/705406#c1
Thanks, I'll give this a go and see what the build time differences are like. I always thought the extra
build phase was unnecessary for typical builds, but I never recalled gcc having this switch before. I don't
exactly play around in its internals much these days, so I probably missed its addition.
Any thought been given to making it into a feature controlled by a USE flag? E.g., 'full-bootstrap' or
something, defaulting to on, to build all three stages, and users can turn it off to skip the comparison stage?
--
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
next prev parent reply other threads:[~2023-06-15 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 4:02 [gentoo-dev] What happened to gcc-12.3.0? Joshua Kinard
2023-06-15 5:04 ` Matt Turner
2023-06-15 15:47 ` Joshua Kinard [this message]
2023-06-15 11:37 ` Sam James
2023-06-15 16:29 ` Joshua Kinard
2023-06-15 15:09 ` Andreas K. Huettel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3b2b943-289a-e256-7c71-5b7cd32b2de7@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox