On Thu, 2010-07-08 at 18:17 -0700, Roland McGrath wrote:
> Is there a way to include pre-packaged workloads analysis? I
realise
> we'd have to regenerate these somehow possible for each compiler update
> (not sure how the files look).
What a "workload" means to the compiler is all the results of all the
conditional branches in the compiled code. What sites there are to have
data points and what the association between those and any high-level
notion of "workload" (i.e. all forms of input to the program) changes not
only with compiler differences, but with every source code change.
It's pretty hard to imagine what you could preserve across builds of
nontrivially nonidentical source trees that would continue to line up at
the basic block level where it's meaningful to the compiler. Perhaps you
could do something reduced to terms of source line locations, or number of
basic blocks into a named function, or something. But it sounds very iffy.
I don't mean to preserve it across different builds, just across one
build, so we do GUI stuff offline without having our koji/brew system
need X installed and the ensuing issues we'll get with executing
processes on it, not to mention koji/brew runs on an EL5 kernel, which
may for things like glibc generate different codepaths than a Fedora
kernel.
So I'd package up stuff, do a koji build, download it, run my
representative test suite, upload the result and do another build.
Dave.