On Tuesday 04 November 2003 21:51, Jonathan Richards wrote: > On Tuesday 04 Nov 2003 7:02 pm, Lee Elliott wrote: > <snip> > > > > What is the effect of adding --build to ./configure? > > > > I already set the appropriate -march, -mfpmath and -msse flags for > > compilation - does the --build option just invoke some of these flags or > > does it do something else? > > > > LeeE > > > I just tried it... > # make clean > # ./configure --with-threads --build=athlon > > Configure reports that it is building for an i686-pc-none or something like > that... > > #make > > This gives me an fgfs that is only a few hundred bytes bigger than the > previous one. > Sitting at the default start location on 28R at KSFO with the engine running > and the brakes on, with the external view from directly astern of the default > Cessna, I was getting 25 fps, and now I get 30 fps. A low orbit around > beautiful downtown San Francisco rarely pulls the framerate below 17 fps, > which is better than before, but nothing dramatic. Note that this is only FG > recompiled with the =athlon switch but it's a generic config option; next > time I do SimGear+plib+FG I'll apply it to all and see if there's a > noticeable difference. Somewhere, there will be information about how gcc > optimizes for i686 as opposed to i386, which I suppose is what it uses > normally. I would expect that -march=athlon has the same effect...? > > Jonathan
I just checked and I actually use -march=athlon-xp -m3dnow -mfpmath=sse. The -march=athlon-xp imples -mcpu=athlon-xp, according to TFM. Dunno if this the same stuff as invoked by --build=athlon. I can't see any other gcc/g++ stuff that might apply. LeeE _______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users
