Hi, there is a forum topic discussing compiler optimization to improve frame rate ( http://www.flightgear.org/forums/viewtopic.php?f=45&p=96830 ). I have also tried this (and successfully improved mine... :-) ).
However, I also compiled with "-Wall" and this shows several issues with the FlightGear sources. Simgear is really clean though (no warnings with g++ 4.4, *clapclap*). I'm seeing 55 warnings with FlightGear: mainly (potential) usage of uninitialized variables and violations of strict aliasing. The latter easily results in broken code when optimizing with "-O2" or above (oh no, "-O2" is the FlightGear default!). Well, and there is another 54 warnings in the AI module, but only since the member variables aren't initialized in the sequence of their declaration (very easily fixed). Since simgear/flightgear already look quite good, it shouldn't get too messy if we allowed the compiler to report more/all warnings by default. So, should we add "-Wall" (or something more specific) to the makefiles' default compiler settings? This ensures all developers immediately see if potential problems with their new code are reported. Of course, it still depends on the specific compiler version one uses - but it's better than to ignore these warnings completely. cheers, Thorsten ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
