On Mon, Oct 26, 2009 at 4:14 AM, James Turner <zakal...@mac.com> wrote:
> If it's an optimisation-related bug, tracing it is going to be pretty
> awful. That said, the crash seems rather widespread for a straight
> compiler issue. I'm also surprised that a compiler bug would change
> frequency based on compile options.
>
In my experience 99.99% of "optimization" bugs are not the compiler's
fault. Usually there is a code problem and for whatever reason, we skate by
with one set of options, but not another depending on how the compiler
arranges or pads the code. If turning off optimization makes a problem go
away, that's a *huge* tip that there is likely a problem in our code. It
would be interesting to see what the back trace is with optimization turned
on.
> I hate optimiser bugs :(
>
I have yet to see one in the wild myself.
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
