------- Comment #7 from t66667 at gmail dot com 2009-12-25 02:46 ------- (In reply to comment #3) > Some issues with -foptimize-sibling-calls were fixed in GCC 4.5 > False. Browsed all recently committed gcc svn change-logs saw no -foptimize-sibling-calls related fixes. Updated gcc-trunk svn, compiled gcc-trunk. Tested gcc version 4.5.0 20091224 (experimental) Revision 155461 MINGW64-1684 Referential numerous bug-reports: * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41424 * http://sourceforge.net/projects/mingw-w64/forums/forum/723797/topic/3482477 Very mingw-w64 specific I think.
-- t66667 at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |4.4.3 4.5.0 Summary|Function call never happened|Opt bug -foptimize-sibling- |after compile with - |calls function call stalled! |foptimize-sibling-calls |dead-lock, cpu max Version|4.4.3 |4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42489