➜

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 skrah
Recipients alecsandru.patrascu, brett.cannon, gregory.p.smith, lemburg, methane, pitrou, r.david.murray, scoder, skrah, steve.dower, vstinner, zach.ware
Date 2016-04-14.08:55:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20160414085513.GA4115@bytereef.org>
In-reply-to <1460623160.19.0.635787464978.issue25702@psf.upfronthosting.co.za>
Content 
On Thu, Apr 14, 2016 at 08:39:20AM +0000, Alecsandru Patrascu wrote:
> @Stefan and @Marc, you say that people don't want to wait for PGO to build when running ./configure && make, but why? Even though many developers use it, this mode is not intended for development, it is production level and should be run once (or at leas a limited number or times), when the developers are sure that everything is fine in the debug mode. As Victor previously said, we should have all the *good* stuff (PGO, LTO, etc) enabled by default, regardless the time needed to do it.

I use it all the time in development:

  - For running math tests that would be too slow otherwise.

  - To diagnose invalid accesses that only occur with -O2.

  - To speed up Valgrind runs.
History
Date User Action Args
2016-04-14 08:55:25skrahsetrecipients: + skrah, lemburg, brett.cannon, gregory.p.smith, pitrou, scoder, vstinner, r.david.murray, methane, zach.ware, steve.dower, alecsandru.patrascu
2016-04-14 08:55:25skrahlinkissue25702 messages
2016-04-14 08:55:25skrahcreate