> From: [EMAIL PROTECTED] On Behalf Of Dave Korn > Sent: Thursday, June 28, 2007 1:39 PM > To: [email protected] > Subject: RE: possible compiler optimization error > > On 28 June 2007 18:19, Frederich, Eric P21322 wrote: > > Your code has a bug, most likely an uninitialised or otherwise stray > pointer, but could be anything that causes undefined > behaviour. It works on > Linux/Solaris by good fortune, because whatever memory > addresses you're > stomping all over just happen to be free and safe to stomp on on those > platforms, whereas windows systems have different process > space layout
During development of this program I used Valgrind on Linux to detect memory allocation and un-initialized pointer type of errors. I do not believe this is the case. > Now, there /could/ be a compiler bug, but unless you can > present us with a > testcase that we can compile ourselves and test out, it's not > going to be easy > to help you. Fragmentary code snippets aren't useful. For > advice on how to > write a really good compiler bug report, see the guidelines at Yes, I do realize this. I figured that describing the behavior would be enough to diagnose the problem without having to cut down an 8,000 line program into a concise example. It turns out that it was and Brian Dessent suggested some more compiler flags to help with floating point accuracy, -ffloat-store. Thanks for your help. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
