-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/08/2010 06:44 PM, Dave Airlie wrote: > So I'd package up stuff, do a koji build, download it, run my > representative test suite, upload the result and do another build. As Roland wrote, if you cannot provide a self-contained RPM build process it'll be tricky setting up the environment and then collection the files. And then you also have to be sure you're using *exactly* the same build environment for the second compile path. That's something which I also don't see koji providing. A new build root will be produced from the then-up-to-date RPMs listed as BuildRequires. There is no bookkeeping of the RPMs used in the first build. If anything is different you won't get the desired effect. But this doesn't mean no package can use PGO. Those where the workload runs can be performed on the build machines it's reasonably easy to perform the optimization. This should, for instance, be done for all scripting languages. These packages hopefully contain test suites which can serve as the beginning of a workload body. Additional code could be collected in new packages (like, for instance, bash-workload) which could be added as BuildRequires if compiling with PGO is wanted. - -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkw2yR4ACgkQ2ijCOnn/RHSmkQCfZ1XwjkeclQ12vXkSPu8kXYse e34An0+t85ce1jJeqrmKgmBZjUqDaHZg =/Aeu -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
