emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#23077: closed (Perl's closure is too big)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#23077: closed (Perl's closure is too big)
Date: Wed, 06 Apr 2016 21:04:01 +0000

Your message dated Wed, 06 Apr 2016 23:03:44 +0200
with message-id <address@hidden>
and subject line Re: bug#23077: Perl's closure is too big
has caused the debbugs.gnu.org bug report #23077,
regarding Perl's closure is too big
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
23077: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23077
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Perl's closure is too big Date: Mon, 21 Mar 2016 09:30:26 -0400
If you run 'guix size perl' you will notice that, as of this writing,
138.2MiB of Perls' 307.6MiB closure is due to referencing gcc's
default output in '/lib/perl5/5.22.1/x86_64-linux/Config_heavy.pl'.
Perl's large closure inflates the closures of many other packages,
such as openssl.

Does anyone familiar with Perl know if we really need to a reference
to GCC here?  Would be great to remove it. :)

- Dave



--- End Message ---
--- Begin Message --- Subject: Re: bug#23077: Perl's closure is too big Date: Wed, 06 Apr 2016 23:03:44 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
"Thompson, David" <address@hidden> skribis:

> If you run 'guix size perl' you will notice that, as of this writing,
> 138.2MiB of Perls' 307.6MiB closure is due to referencing gcc's
> default output in '/lib/perl5/5.22.1/x86_64-linux/Config_heavy.pl'.
> Perl's large closure inflates the closures of many other packages,
> such as openssl.

Fixed in 81cea47d4a4c0054beb234004b990d6f514d0514 on ‘core-updates’.

Most likely this was a regression introduced with the upgrade to 5.22 in
4de35074833742e45237464bb1727ce1a55f3336.  Previously the issue had been
addressed in f727ec5bc8a6f97ae1083026e508b917235dfd2d.

Thanks,
Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]