Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!feeder-out5.eu1.usenetexpress.com!feeder.usenetexpress.com!feeder-in1.eu1.usenetexpress.com!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod
From: Matthias Klose <doko@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Profile-guided optimisation / link-time optimisation in Buster
Date: Mon, 23 Apr 2018 09:20:01 +0200
Message-ID: <vHDVv-70R-3@gated-at.bofh.it>
References: <vHtjs-8kM-7@gated-at.bofh.it>
X-Original-To: Matthew Woodcraft <matthew@woodcraft.me.uk>, debian-python@lists.debian.org
X-Mailbox-Line: From debian-python-request@lists.debian.org  Mon Apr 23 07:11:28 2018
Old-Return-Path: <doko@debian.org>
X-Amavis-Spam-Status: No, score=-7.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate:hard: -5
X-Greylist: delayed 337 seconds by postgrey-1.36 at bendel; Mon, 23 Apr 2018 07:11:13 UTC
Old-X-Envelope-From: doko@debian.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/15838
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/add304b7-93de-e1cd-d6b5-43eba526a64d@debian.org
Approved: robomod@news.nic.it
Lines: 24
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Mon, 23 Apr 2018 09:05:08 +0200
X-Original-Message-ID: <add304b7-93de-e1cd-d6b5-43eba526a64d@debian.org>
X-Original-References: <1524425483.otum83bz9j.astroid@golux.woodcraft.me.uk>
Xref: csiph.com linux.debian.maint.python:10437

On 22.04.2018 21:31, Matthew Woodcraft wrote:
> I noticed that profile-guided optimisation and link-time optimisation
> have both been unconditionally disabled in Buster's Python 3.6 and 3.7
> packages, though 3.5 in Stretch had them both enabled (on common
> platforms).
> 
> Can anyone tell me why this was done?
> 
> 
> I see nothing about this in debian/changelog and the indentation in
> debian/rules looks odd, so I'm wondering if it might even have been an
> unintentional change.
> 
> 
> It's these extra lines in debian/rules:
> 
>    with_pgo =
>    with_lto =
> 
> just before the
>  ifeq ($(with_lto),yes)
> line.

yep, will turn it on again.