[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210502175510.GB4522@localhost>
Date: Sun, 2 May 2021 20:55:10 +0300
From: Adrian Bunk <bunk@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Tom Stellard <tstellar@...hat.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Fangrui Song <maskray@...gle.com>,
Serge Guelton <sguelton@...hat.com>,
Sylvestre Ledru <sylvestre@...illa.com>
Subject: Re: Very slow clang kernel config ..
On Sun, May 02, 2021 at 09:49:44AM -0700, Linus Torvalds wrote:
> On Sun, May 2, 2021 at 9:45 AM Adrian Bunk <bunk@...nel.org> wrote:
> >
> > Mesa and PostgreSQL are among the packages that do use libLLVM.so,
> > this is a popular library for implementing compilers and JITs.
>
> Yes, and it's entirely reasonable to update those packages if it turns
> out libLLVM has a bug in it.
>
> Because we're talking about a small handful of packages, not some kind
> of "everything" model.
>
> So again, what's your point?
Two dozen other packages are linking directly with libLLVM.so.
Are you happy about libclang.so being a shared library?
libclang.so uses libLLVM.so, which adds another 10 indirect users.
Debian ships 30k source packages that build 60k binary packages,
with 3 years of security support (plus 2 years LTS).
It makes things a lot easier from a distribution point of view if a bug
in libLLVM can be fixed just there, instead of having to additionally
find and rebuild the 30 or more source packages building binary packages
that use libLLVM in a security update for a stable release of a distribution.
> Linus
cu
Adrian
Powered by blists - more mailing lists