enable PGO for gcc.
instead of building twice in the same build dir (which if there's an error can lead to using the -fprofile-generate thinking it's the -fprofile-use build), we build the -fprofile-generate build as pyston_release_gcc_pgo. The resulting -fprofile-use build is the normal pyston_release_gcc build. Deps aren't quite there yet, but this should also allows you to re-train the pgo build later and then apply the new data to the release build, e.g.: ``` $ rm -f ./build/Release-gcc $ ./pyston_release_gcc_pgo ${training.py} $ make pyston_release_gcc ```
Showing
Please register or sign in to comment