Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10436
| From | Matthew Woodcraft <matthew@woodcraft.me.uk> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Profile-guided optimisation / link-time optimisation in Buster |
| Date | 2018-04-22 22:00 +0200 |
| Message-ID | <vHtjs-8kM-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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.
-M-
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread
Profile-guided optimisation / link-time optimisation in Buster Matthew Woodcraft <matthew@woodcraft.me.uk> - 2018-04-22 22:00 +0200 Re: Profile-guided optimisation / link-time optimisation in Buster Matthias Klose <doko@debian.org> - 2018-04-23 09:20 +0200
csiph-web