On Fri, Jul 09, 2010 at 05:50:24PM +0200, Jakub Jelinek wrote: > On Fri, Jul 09, 2010 at 11:36:04AM -0400, David Malcolm wrote: > > Python has a benchmarking suite that tries to reflect real-world > > workloads, and I've filed > > https://bugzilla.redhat.com/show_bug.cgi?id=613045 > > "RFE: Add profile guided optimization to our builds of Python 2" > > and https://bugzilla.redhat.com/show_bug.cgi?id=613046 > > "RFE: Add profile guided optimization to our builds of Python 3" > > > > Help doing this for Python would be welcome, though it may be better to > > focus on python3 for now, until after the 2.6 to 2.7 transition is done. > > Thanks. Googling for %cflags_profile_generate (something OpenSUSE uses > in spec files using PGO) reveals that at least bash, openssl, gawk > use PGO in their distro, guess e.g. grep, sed or even rpm would be > other useful packages for start. > Say for bash it is a matter of doing > make CFLAGS="%{optflags} -fprofile-generate" all > make ... check > make CFLAGS="%{optflags} -fprofile-use" all > (for some packages might require some minor makefile changes or something > similar). > One wrinkle in this specific to python is that python's distutils provides an easy way to build third party extensions and it uses the CFLAGS that were used to build python itself. If -fprofile-use is a no-op when there's no profile information it's probably harmless. If not, then we probably need to sed that out of the Makefile that gets installed on the system. -Toshio
Attachment:
pgpgwC1NW9nPQ.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
