From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Reducing LLVM closure size
Date: Sun, 28 Jun 2020 22:30:53 +0200 [thread overview]
Message-ID: <87y2o7exvm.fsf@gnu.org> (raw)
In-Reply-To: <87lfkerx66.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Tue, 23 Jun 2020 10:41:53 +0200")
Hi,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> 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?
>
> Friendly ping :)
> Should I send a patch?
Yes, please!
Ludo’.
next prev parent reply other threads:[~2020-06-28 20:31 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
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 [this message]
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
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=87y2o7exvm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).