This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/38792] RFE - Need Makefile to build using different strategy for "coverage" vs. "profiling"
- From: "rob1weld at aol dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Jan 2009 14:53:09 -0000
- Subject: [Bug bootstrap/38792] RFE - Need Makefile to build using different strategy for "coverage" vs. "profiling"
- References: <bug-38792-13830@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from rob1weld at aol dot com 2009-01-13 14:53 -------
(In reply to comment #3)
> Coverage builds should not be bootstrapped.
>
> Profiled bootstrap means build stage1 with no opts and then stage2 with
> generating the profiling data and then build some target libraries (not all
> though) and the build stage3 using that generated profile data.
>
For "Coverage" I used the additional ./configure option of
"--enable-coverage=noopt" and initiated the 'make' by typing "gmake".
For "Profiling" I used no additional ./configure options and initiated
the 'make' by typing "gmake profiledbootstrap".
Rob
PS: I did succeed in compiling gcc and it's libraries with the "coverage"
options: "-fprofile-arcs -ftest-coverage" and now when I run the Testsuite
I get coverage stats in my executable's directory.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38792