As w64 has to take care about aligned stack after function epilogue the frame variable frame.padding0 was introduced. But much code just checks for frame.to_allocate without the optional padding, in some cases register save regions are calculated wrongly and lead to register clobbering in an unintended way.
-- Summary: frame.padding0 isn't treat in all cases of i386 Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ktietz at gcc dot gnu dot org GCC target triplet: x86_64-*-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41315