From mint-bounce@lists.fishpool.fi Wed Dec 9 08:54:57 2009 Message-ID: <4B1FAB84.1000009@atari-source.org> Date: Wed, 09 Dec 2009 08:52:04 -0500 From: Mark Duckworth User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Eero Tamminen CC: mint@lists.fishpool.fi Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <1260278588.20336.221.camel@jetpack.demon.co.uk> <4B1E5596.9010300@freesbee.fr> <200912082209.08699.oak@helsinkinet.fi> In-Reply-To: <200912082209.08699.oak@helsinkinet.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Eero Tamminen wrote: > Hi, > > On Tuesday 08 December 2009, Vincent Rivière wrote: > >> Alan Hourihane wrote: >> >>> One of the easiest things to do is add -fno-strict-aliasing and see if >>> that helps. If that does it should be pretty easy to track down. >>> >> Exactly. >> >> And if this not enough, all the -O options have to be removed. Most >> compiler issues disappear when all the optimizations are turned off. >> > > I wouldn't still call them issues in compiler... To be able to do > optimizations, compiler needs to be able to assume that the code > it's compiling is correct. If the code isn't correct, funny things can > happen after optimizations. > > > >> But the real cause is usually a hidden bug in the sources of the >> problematic software. We can't exclude a compiler bug, too, but it is >> more rare. >> > > I think during well over ten years of programming C-code, I've seen only > couple of issue that were bugs in GCC code generation and not in the > compiled C-code and those have been associated with support for some > new architecture / instruction set in it. > > GCC C++ side has AFAIK had more issues, but I don't really code C++, > so I've been saved from those. GCC can also sometimes terminate to > an ICE i.e. internal compiler error, but those don't generate bad code > and are also exceedingly rare. > > > - Eero > > > I've never seen a GCC ICE that wasn't some kind of unreliable hardware problem. I used to get them when my falcon was overclocked too high. Thanks, Mark