Re: [SOLVED] Re: [Qemu-devel] Overoptimization

[Lionel Ulmer]

> In fact I just had to read the gcc info page and remove optimizations 
> one by one. Result, with gcc 3.3.2:
> 
> -Wall -O2 -g -fomit-frame-pointer (defaults) = unsafe,
> -Wall -O2 -g -fomit-frame-pointer -fno-strict-aliasing = safe.
> 
> So it looks like slirp code breaks strict aliasing rules assumed by -O2. 
> Since the problem has been identified precisely, it has to be fixed in 
> qemu CVS.

I think this aliasing stuff will really provoke a LOT of bugs out there for
years to come...

For example, Wine switched to '-fno-strict-aliasing' a long time ago :-)

        Lionel

-- 
                 Lionel Ulmer - http://www.bbrox.org/