Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-08-04 Thread Santiago Vila
On Thu, 4 Aug 2016, Santiago Vila wrote: > In particular, the size of "lto1" went from 20 MB to 144 MB. > Is this really normal/expected? Hmm, lto1 was stripped in GCC 5 (stretch) and now it's unstripped again (sid, GCC 6). Is this intended or accidental? Thanks.

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-08-04 Thread Santiago Vila
Hello Matthias. With GCC 6 as the default, the size of a minimal build system has grown by about 150 MB. In particular, the size of "lto1" went from 20 MB to 144 MB. Is this really normal/expected? While we are at it, this bug is marked as "forwarded". Are there any news from the upstream mainta

Bug#783876: Fwd: Re: Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-04-21 Thread Basile Starynkevitch
On 04/22/2016 12:11 AM, Santiago Vila wrote: On Thu, 30 Apr 2015, Matthias Klose 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 abo

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-04-21 Thread Basile Starynkevitch
On 04/22/2016 12:11 AM, Santiago Vila wrote: On Thu, 30 Apr 2015, Matthias Klose 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 abou

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-04-21 Thread Matthias Klose
On 22.04.2016 00:55, Santiago Vila wrote: On Fri, Apr 22, 2016 at 12:22:33AM +0200, Matthias Klose wrote: On 22.04.2016 00:11, Santiago Vila wrote: The problem with that is that it breaks the expectation that testing is in an "always releaseable" state. Sure, the file /etc/debian_version break

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-04-21 Thread Santiago Vila
On Fri, Apr 22, 2016 at 12:22:33AM +0200, Matthias Klose wrote: > On 22.04.2016 00:11, Santiago Vila wrote: > >The problem with that is that it breaks the expectation that testing > >is in an "always releaseable" state. > > > >Sure, the file /etc/debian_version breaks such expectation too, but of >

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-04-21 Thread Matthias Klose
On 22.04.2016 00:11, Santiago Vila wrote: On Thu, 30 Apr 2015, Matthias Klose 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 1

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2016-04-21 Thread Santiago Vila
On Thu, 30 Apr 2015, Matthias Klose 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

Processed: Re: Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-08-09 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://gcc.gnu.org/PR67165 Bug #783876 [gcc-5] gcc-5: consider stripping lto1 / cc1 / cc1plus Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR67165'. -- 783876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783876 Debian Bug Tracking System

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-08-09 Thread Matthias Klose
Control: forwarded -1 https://gcc.gnu.org/PR67165 On 08/03/2015 10:26 AM, Aurelien Jarno wrote: > On 2015-08-03 09:57, Basile Starynkevitch wrote: >> I would believe that is not easily possible. I don't know the detailed >> behavior of libbacktrace, but it is using & parsing the DWARF debug >> inf

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-08-03 Thread Aurelien Jarno
On 2015-08-03 09:57, Basile Starynkevitch wrote: > On Mon, Aug 03, 2015 at 09:47:33AM +0200, Aurelien Jarno wrote: > > On 2015-04-30 23:10, Matthias Klose wrote: > > > On 04/30/2015 10:43 PM, Daniel Serpell wrote: > > > > Currently, gcc-5 packages are really big because the files under > > > > /usr

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-08-03 Thread Basile Starynkevitch
On Mon, Aug 03, 2015 at 09:47:33AM +0200, Aurelien Jarno wrote: > On 2015-04-30 23:10, Matthias Klose 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

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-08-03 Thread Aurelien Jarno
On 2015-04-30 23:10, Matthias Klose 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

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-07-12 Thread Guillem Jover
Hi! On Fri, 2015-07-10 at 09:22:25 +0200, Basile Starynkevitch wrote: > 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 ? I've not checked how plugins are implemented in gc

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-07-10 Thread Basile Starynkevitch
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 wrote: > >> On 04/30/2015 10:43 PM, Daniel Serpell wrote: > >>> Currently, gcc-5 packages are really big because the files under > >>

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-07-07 Thread Matthias Klose
On 07/04/2015 04:23 PM, Josh Triplett wrote: > On Thu, 30 Apr 2015 23:10:15 +0200 Matthias Klose 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 >>> lt

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-07-04 Thread Josh Triplett
On Thu, 30 Apr 2015 23:10:15 +0200 Matthias Klose 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. > > > > Ple

Re: Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-06-28 Thread Basile Starynkevitch
On 06/28/2015 05:52 PM, Guillem Jover wrote: Hi! On Thu, 2015-04-30 at 17:43:00 -0300, Daniel Serpell wrote: Package: gcc-5 Version: 5.1.1-2 Severity: wishlist 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

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-06-28 Thread Guillem Jover
Hi! On Thu, 2015-04-30 at 17:43:00 -0300, Daniel Serpell wrote: > Package: gcc-5 > Version: 5.1.1-2 > Severity: wishlist > 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. >

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-04-30 Thread Matthias Klose
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

Bug#783876: gcc-5: consider stripping lto1 / cc1 / cc1plus

2015-04-30 Thread Daniel Serpell
Package: gcc-5 Version: 5.1.1-2 Severity: wishlist Dear Maintainer, 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 installat