From: "Ludovic Courtès" <ludo@gnu.org>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: guix-devel@gnu.org
Subject: Re: gcc: build all languages at once?
Date: Wed, 08 Sep 2021 23:08:44 +0200 [thread overview]
Message-ID: <87r1dyzsf7.fsf@gnu.org> (raw)
In-Reply-To: <86czpt1pe6.fsf@mgsn.dev> (Sarah Morgensen's message of "Tue, 31 Aug 2021 10:43:13 -0700")
Hi Sarah,
Sarah Morgensen <iskarian@mgsn.dev> skribis:
> I notice that out of GCC's supported languages (ada, c, c++, d, fortran,
> go, jit, lto, objc, obj-c++) we currently build all except ada, and five
> of them (d, fortran, go, objc, and obj-c++) are built separately. Most
> of GCC's build time is spent bootstrapping and building the actual
> compiler, rather than building the frontends, so we would save a lot of
> build time by building them all together.
Yes, but at the expense of the build time of the main GCC package and of
its size.
> We could also possibly reuse the 'core' parts of GCC between language
> frontends, saving some space. (This is what distros seem to do.)
That’d be ideal, but I’m not sure it’s feasible. It’s feasible for FHS
distros that “just” need to shuffle files around in various binary
packages, but here we’d have to have several outputs or something, and
most likely they’d refer to one another.
> If we do this, I'm not sure whether it would be better to have each
> additional language as an output for gcc, or as a separate package.
>
> Currently, the only build-time difference between our GCC packages is
> that our package for 'jit' uses '--enable-host-shared', which
> "[specifies] that the host code should be built into
> position-independent machine code (with -fPIC), allowing it to be used
> within shared libraries, but yielding a slightly slower compiler" [0].
> I don't think it would be too big of a hit to just turn that on
> unconditionally, but we could also keep 'jit' as a separately-built
> package.
Yeah, dunno.
> What do you all think?
There’s definitely room for improvement in this area, but it’s not clear
to me what can be done within the constraints that we have, in
particular the closure size of gcc (gcc:lib in particular) and having a
reasonably small set of dependencies for ‘gcc-final’. I suppose
experimentation could tell us which approach to follow!
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-09-08 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 17:43 gcc: build all languages at once? Sarah Morgensen
2021-09-08 21:08 ` Ludovic Courtès [this message]
2021-09-09 10:14 ` Maxime Devos
2021-09-10 19:59 ` Sarah Morgensen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1dyzsf7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iskarian@mgsn.dev \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).