Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus
On Tue, Jul 07, 2015 at 11:08:13AM +0200, Matthias Klose wrote:
> On 07/04/2015 04:23 PM, Josh Triplett wrote:
> > On Thu, 30 Apr 2015 23:10:15 +0200 Matthias Klose <doko@debian.org> wrote:
> >> On 04/30/2015 10:43 PM, Daniel Serpell wrote:
> >>> Currently, gcc-5 packages are really big because the files under
> >>> /usr/lib/gcc/x86_64-linux-gnu/5 are not stripped, and each one of
> >>> lto1, cc1 and cc1plus is about 130MB.
> >>>
> >>> Please, can those files be striped in the default installation?
> >>
> >> I'd like to avoid this, and only change that near the next Debian release.
> >> These binaries are linked against libbacktrace to provide a verbose backtrace on
> >> internal compiler errors, which you can't get with stripped binaries.
> >
> > Linking against libbacktrace seems completely fine. However, can
> > libbacktrace not use detached debug symbols, as found in -dbg packages?
>
> No.
>
> Plus, Basile mentions that plugins won't work anymore with stripped binaries,
> however I fail to see why that would be the case. We had clang plugin working in
> the past too.
>
How can a plugin call existing GCC functions, e.g. walk_gimple_seq
declared in
/usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/gimple-walk.h and
implemented inside cc1 ?
(Unless you don't strip the dynamic symbols linked with -rdynamic when building cc1)
Regards.
--
Basile Starynkevitch http://starynkevitch.net/Basile/
France
Reply to: