http://bugs.winehq.org/show_bug.cgi?id=28753
--- Comment #3 from Anastasius Focht focht@gmx.net 2011-10-17 14:22:55 CDT --- Hello Austin,
--- quote --- FWIW, I filed a gcc bug for this about a year ago: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46468 --- quote ---
It was their decision to change the default behaviour for frame pointer optimizations starting with 4.6 series. It's very, very unlikely that the gcc folks will revert this for the sake of Wine.
If Wine depends on the previous behaviour ... it has to take care of this. The generated code is perfectly legal with changed default.
If there is application code, for example copy protection/obfuscation schemes that rely on valid frame pointer being present in certain API code, Wine needs to hint gcc using function annotation or by explicitly changing default behaviour to old state.
Regards