On Sat, Jan 15, 2005 at 08:07:35PM +0100, Kurt Roeckx wrote: > I've let Frederik Schueler run run that test on an dual CPU box > in a loop. He says that all 120 runs of it were succesful. I > also tried it many times myself and they all were succesful too.
That's good news. > If there was a problem, it might have been fixed, or it might not > have been. If a problem only shows once in a while, it's ussualy > a timing issue. Building with a different compiler might > generate different results because of this. I've seen it too > many times that when rebuild without -O or with gdb attached the > problems seem to go away. Compilation with a different compiler > can have the same effect. That does not mean the problem isn't > there anymore, it just means it's now showing up in the tests you > do. I doubt in this case gcc-3.4 solved anything. For that reason I tried different compilation options, and different versions of gcc, on both platforms, with consistent results. None of which means anything; without knowing what the problem was it's all a guess. Happy computing, --Pete -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
