[Python-Dev] FYI: Python 2.7.1 + gcc 4.6 (experimental) probable optimizer problem

["Martin v. Löwis"]

> BTW: I've been doing gcc pre-release testing regularly for many year, starting 
> with gcc 3.3. This is the first time I see the Python build fail persistently 
> for several weeks.

Wild guess: did configure detect that it needs to use -fno-strict-aliasing?

Regards,
Martin