[Bug target/57982] GetModuleHandle in __register_frame_info causes abort on unload
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57982 Jean-Pierre Flori jpflori at gmail dot com changed: What|Removed |Added CC||jpflori at gmail dot com --- Comment #2 from Jean-Pierre Flori jpflori at gmail dot com --- (In reply to Kai Tietz from comment #1) Ups, this bug didn't shown up in my search-list ... Issue fixed for 4.7, 4.8, and trunk at rev 204635-204637. I recently stumbled on a similar problem again with a recent Cygwin/GCC combination. Looking at the fix included in GCC, it does look slightly different from what was first suggested here. Could someone more knowledgeable than me have a look and tell whether the included fix is fine or incomplete? If incomplete, I'll be happy to open a new bug report. See here for my report on cygwin's mailing-list: https://cygwin.com/ml/cygwin-apps/2015-01/msg00062.html
[Bug target/57680] [META-BUG][target]deregister_frame_fn is set to invalid address in cygming-crtbegin.c:__gcc_deregister_frame due to unknown reason.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57680 Jean-Pierre Flori jpflori at gmail dot com changed: What|Removed |Added CC||jpflori at gmail dot com --- Comment #3 from Jean-Pierre Flori jpflori at gmail dot com --- This looks like the problem reported here: * http://cygwin.com/ml/cygwin/2013-08/msg00201.html * ​http://cygwin.com/ml/cygwin/2013-07/msg00528.html Note that an explanation and a fix are also provided there. This also affects 4.7.3.
[Bug target/52061] compiler internal error in extract_insn
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52061 --- Comment #2 from Jean-Pierre Flori jpflori at gmail dot com 2013-01-03 22:50:50 UTC --- This is fixed with FSF GCC 4.7.2.
[Bug target/52061] compiler internal error in extract_insn
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52061 Jean-Pierre Flori jpflori at gmail dot com changed: What|Removed |Added CC||jpflori at gmail dot com --- Comment #1 from Jean-Pierre Flori jpflori at gmail dot com 2012-12-21 10:32:10 UTC --- I can confirm this also happens on the current Cygwin distribution with GCC 4.6.3 bootstrapped with the Cygwin GCC 4.5.3 distributed in the gcc4 package. I'm trying to build GCC 4.7.2 to see whether the bug is still present there.