Created attachment 320912 [details, diff]
Currently, Python 2.7.3 is being built with -fno-strict-aliasing. Python 3.x has been patched at upstream to avoid -fno-strict-aliasing and the back can be trivially backported to Python 2.7.3.
I have attached the backported patch. It provides performance benefits to anyone using GCC 4.3 or later.
Looks ok to me.
Do we want to add this to the patchset, or just stick it in FILESDIR?
(In reply to comment #1)
> Looks ok to me.
> Do we want to add this to the patchset, or just stick it in FILESDIR?
It looks like all of the python 2.7.3 patches are in the patch set. It probably would be best to add it there.
IIRC, those warnings are *not* false positives in <3.0 - there's a common macro in 2.x, that does violate strict aliasing and *does* produce wrong code then.
You'd better ask Arfrever to be sure.
This patch is unacceptable.
A part of API of Python 2 is incompatible with strict-aliasing rules.
This bug should then be closed