http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60830
--- Comment #22 from Kai Tietz <ktietz at gcc dot gnu.org> --- (In reply to Denis Excoffier from comment #21) > (In reply to Kai Tietz from comment #17) > > Just as side-note, I tried to reproduce your reported issue and did a > > personal build of cygwin's gcc. It worked fine in stage2. I couldn't > > reproduce the reported ICE on stage2. Which brings me to the question if > > you are using additional patches/fixes, etc > Did you use 32bits? Did you use a recent cygwin version? There has been some > movement recently (2014-03-28) in dtors.cc, although i believe that only > 64bits is impacted. I built recent gcc 4.9 on my pre-installed cygwin 32-bit (as you did too, as logs have shown). Only difference I made was to disable multilib. And this you should do too. Additionally I built x64 version on my cygwin64 environment too. So from my point of view it isn't a gcc issue. As both targets are bootstrapping without issue for me. So, it might be an issue with recent cygwin, I can test that too. I will continue on that tomorrow as it takes me pretty long to built it native. Nevetheless I doubt that I will find different results for gcc. And if it is really dependent on cygwin-dll version, then it seems to me indeed like a cygwin-bug
