all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Reducing LLVM closure size
Date: Tue, 16 Jun 2020 11:27:45 +0200	[thread overview]
Message-ID: <87eeqficmm.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87zh93wejf.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

>> - either move the libs to a "lib" output,
>> - or move the "bin" and "include" folder to a new output.
>>
>> The second approach has the benefit of being less disruptive for dependents.
>
> I have a slight preference for a “lib” output since that’s more in line
> with what we do for other packages.

OK.

> Nice!  I looked for something like this when I packaged
> ‘clang-tools-extra’ and didn’t find it.  This should go into the next
> ‘staging’ branch (or ‘core-updates’?).

I can send a patch for llvm-10, but I guess many llvm-dependents will
have to be updated accordingly.

I suppose that the input

--8<---------------cut here---------------start------------->8---
("llvm" ,llvm)
--8<---------------cut here---------------end--------------->8---

will need to be turned to

--8<---------------cut here---------------start------------->8---
("llvm" ,llvm "lib")
--8<---------------cut here---------------end--------------->8---

for most packages.  I have no experience with LLVM, so can someone
confirm that this is the right way to go?

>> All in all, it looks like we can save 52 MiB out of 140 MiB from the LLVM
>> package (and 210 MiB from its closure).
>
> That’d be great.

To clarify the ambiguous sentence I wrote above, we would save 52 MiB
from the closure size of LLVM.

> An additional option would be to have a package with fewer backends by
> default (currently all of them are enabled and that takes up quite some
> space).  In particular, Mesa doesn’t depend to depend on an LLVM variant
> with 15 backends when it’s only going to use one.

Are you suggesting an alternative or a tweak to add on top of my
suggestion?

Where would we store the different backends?  In different outputs?
On which backend does Mesa depend for instance?

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-06-16  9:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12  9:06 Reducing LLVM closure size Pierre Neidhardt
2020-06-12 12:01 ` Julien Lepiller
2020-06-12 12:09   ` Oliver Propst
2020-06-12 13:19   ` Pierre Neidhardt
2020-06-12 13:34     ` Julien Lepiller
2020-06-12 14:13       ` Pierre Neidhardt
2020-06-13 12:28 ` Arun Isaac
2020-06-13 15:34   ` Pierre Neidhardt
2020-06-16  9:22 ` Ludovic Courtès
2020-06-16  9:27   ` Pierre Neidhardt [this message]
2020-06-16  9:45     ` Efraim Flashner
2020-06-16 10:11       ` Pierre Neidhardt
2020-07-07  8:49       ` Pierre Neidhardt
2020-06-23  8:41     ` Pierre Neidhardt
2020-06-28 20:30       ` Ludovic Courtès
2020-07-28 10:09         ` Pierre Neidhardt

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=87eeqficmm.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.