This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Use -fprofile-generate/-fprofile-use for profiledbootstrap
- From: Jan Hubicka <jh at suse dot cz>
- To: gcc-patches at gcc dot gnu dot org
- Date: Tue, 6 Jan 2004 23:48:46 +0100
- Subject: Use -fprofile-generate/-fprofile-use for profiledbootstrap
Hi,
I've profiledbootstrapped the attached patch and commited.
The resulting compiler is slightly faster than with
-fbranch-probabilities only, the difference is about 8 seconds on
Gerald's testcase.
2004-01-06 Jan Hubicka <jh@suse.cz>
* Makefile.in (STAGEPROFILE_FLAGS_TO_PASS): Use -fprofile-generate
* Makefile.in (STAGEFEEDBACK_FLAGS_TO_PASS): Use -fprofile-use
Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/Makefile.in,v
retrieving revision 1.1215
diff -c -3 -p -r1.1215 Makefile.in
*** Makefile.in 4 Jan 2004 14:39:11 -0000 1.1215
--- Makefile.in 6 Jan 2004 22:45:42 -0000
*************** STAGE2_FLAGS_TO_PASS = \
*** 3339,3350 ****
WERROR="@WERROR@" \
STAGEPROFILE_FLAGS_TO_PASS = \
! CFLAGS="$(BOOT_CFLAGS) -fprofile-arcs"
# Files never linked into the final executable produces warnings about missing
# profile.
STAGEFEEDBACK_FLAGS_TO_PASS = \
! CFLAGS="$(BOOT_CFLAGS) -fbranch-probabilities"
# Only build the C compiler for stage1, because that is the only one that
# we can guarantee will build with the native compiler, and also it is the
--- 3339,3350 ----
WERROR="@WERROR@" \
STAGEPROFILE_FLAGS_TO_PASS = \
! CFLAGS="$(BOOT_CFLAGS) -fprofile-generate"
# Files never linked into the final executable produces warnings about missing
# profile.
STAGEFEEDBACK_FLAGS_TO_PASS = \
! CFLAGS="$(BOOT_CFLAGS) -fprofile-use"
# Only build the C compiler for stage1, because that is the only one that
# we can guarantee will build with the native compiler, and also it is the