public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* bootstrapping with profiling feedback?
@ 2002-07-26  7:05 Jeff Garzik
  2002-07-30  5:50 ` Nix
  0 siblings, 1 reply; 2+ messages in thread
From: Jeff Garzik @ 2002-07-26  7:05 UTC (permalink / raw)
  To: gcc

Has anyone done any work towards inserting a -fprofile-arcs step into 
"make bootstrap"?  A search of gcc and gcc-patches list archives didn't 
reveal anything immediately...

I'm assuming an implementation would look something like:

build stage1 using platform compiler
build stage2 using stage1 and -fprofile-arcs
build stage3 using stage2 and -fbranch-probabilities
build stage4 using stage3 and -fbranch-probabilities
compare stage 3 and 4 .o files

Maybe this could be called "make profilestrap"?  ;-)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: bootstrapping with profiling feedback?
  2002-07-26  7:05 bootstrapping with profiling feedback? Jeff Garzik
@ 2002-07-30  5:50 ` Nix
  0 siblings, 0 replies; 2+ messages in thread
From: Nix @ 2002-07-30  5:50 UTC (permalink / raw)
  To: Jeff Garzik; +Cc: gcc

On Thu, 25 Jul 2002, Jeff Garzik spake:
> I'm assuming an implementation would look something like:
> 
> build stage1 using platform compiler
> build stage2 using stage1 and -fprofile-arcs
> build stage3 using stage2 and -fbranch-probabilities
> build stage4 using stage3 and -fbranch-probabilities
> compare stage 3 and 4 .o files
> 
> Maybe this could be called "make profilestrap"?  ;-)

I'd like that too; but I'd be just as happy to have a slightly different
target that builds stage1 with -fprofile-arcs -ftest-coverage, and
likewise for everything else (right up tot the libraries and testsuite),
so we can see how much of the (machine-independent and relevant
-dependent) parts of the compiler is actually being tested by a
bootstrap&test run.

(We might have to unconditionally turn off one or all of these flags for
the appropriate parts of profile.c and/or libgcc2.c themselves :) a small
loss, we'll *know* they're being tested...)


Pie-in-the-sky, I dream of a target that just runs the testsuite with a
compiler with test-coverage turned on, but builds libraries and things
without that flag, so we can tell how much of the compiler the testsuite
alone is testing; the whole-lot results might be perturbed by changes in
the compiler, but if we are testing part of the compiler via the
testsuite, it's reasonable to suppose that it'll stay tested :)

-- 
`There's something satisfying about killing JWZ over and over again.'
                                        -- 1i, personal communication

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-07-29 23:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-26  7:05 bootstrapping with profiling feedback? Jeff Garzik
2002-07-30  5:50 ` Nix

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).