On Sat, 2 Aug 2003, Steven M. Schultz wrote: > > From: Ronald Bultje <[EMAIL PROTECTED]> > > Yes, we had that before. I don't know what it was. Either it was a bug > > in nasm (we've had that a few times), or it was a bug in too high > > optimization, or it was something else that was our bug. Try with the > > latest nasm you can get and try latest CVS of jpeg-mmx. > > It was a bug in using too high an optimization level (-O3). As > Bernhard mention (and I discovered a while back) using -O2 (or simply > -O) fixes the problem.
I don't think "fixes" is really the correct term, more appropriate would be "masks". If the code fails with -O3, then there is either A) a bug in the code, or B) a bug in the optimizer. Using a different optimization level level doesn't fix either one. ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
