Where olpc machine spending time when using web broswer

[Adam Jackson]

On Tue, 2007-03-13 at 13:47 -0400, Dan Williams wrote:
> On Tue, 2007-03-13 at 13:22 -0400, Adam Jackson wrote:
> > On Tue, 2007-03-13 at 13:15 -0400, Dan Williams wrote:
> > 
> > > > I already did gcc tunning to geode (pipeline description, code costs, 
> > > > i386 port parameter values) and submitted it to the gcc mainline.  As I 
> > > > know Jakub Julinek was going to backport this code to redhat gcc.  So I 
> > > > can guess that if the right compiler and options are used, it will make 
> > > > code faster (and several % smaller because -mtune=geode generates 
> > > > smaller code that any other tuning).
> > > 
> > > I seem to recall that we have a gcc available that does geode tuning.
> > > What's missing is to change the RPM_OPT_FLAGS in the olpc-1 buildroots
> > > and then fork & recompile packages from package-cvs that we want to
> > > optimize with geode.  That by definition means that we try to recompile
> > > only the smallest set of packages we can since it's a branch off of FC6.
> > 
> > I'm reasonably sure the olpc buildroot has a sufficient gcc for this.
> > FC6's gcc has a patch entitled gcc41-i386-tune-geode.patch.
> > 
> > I'm already doing some custom RPM_OPT_FLAGS action for X, I can add
> > -march=geode and -momit-leaf-frame-pointer if we think it'll help.
> 
> Could you run a build of X with the geode options and we'll get Chris to
> do some benchmarks and see if stuff gets faster?

Done, just -mtune=geode for now as Vladimir suggested, will be in -0.13
in the next image.

- ajax