This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients alecsandru.patrascu, brett.cannon, gregory.p.smith, lemburg, methane, pitrou, r.david.murray, scoder, skrah, steve.dower, zach.ware
Date 2016-03-05.00:44:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457138683.87.0.590546697051.issue25702@psf.upfronthosting.co.za>
In-reply-to
Content
Piping up from the peanut gallery here:

If your use case is not doing release builds for production use, i.e. "casual use", don't bother with either PGO or LTO.  It won't matter.

Your final build that you Q&A ship should absolutely use those. (nobody's going to disagree with that :)

While I would not reject changes that allow --with-lto to work in the absence of PGO, but I don't think it should be anyone's priority.
History
Date User Action Args
2016-03-05 00:44:43gregory.p.smithsetrecipients: + gregory.p.smith, lemburg, brett.cannon, pitrou, scoder, r.david.murray, methane, skrah, zach.ware, steve.dower, alecsandru.patrascu
2016-03-05 00:44:43gregory.p.smithsetmessageid: <1457138683.87.0.590546697051.issue25702@psf.upfronthosting.co.za>
2016-03-05 00:44:43gregory.p.smithlinkissue25702 messages
2016-03-05 00:44:43gregory.p.smithcreate