http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52015
--- Comment #32 from Nathan Ridge <zeratul976 at hotmail dot com> --- (In reply to Jonathan Wakely from comment #31) > Or to put it another way, this bug only affects MinGW users, is blocked by a > limitation in MinGW, and noone from MinGW has offered to do anything about > it, but you're pointing fingers at GCC devs and saying there's a GCC clique? > Who is preventing MinGW devs joining this clique? No one, but they need to know about issues like this in order to do something about them. Above you said that this was "not possible" to fix for mingw. If you really meant "this would require changes in the mingw runtime", perhaps you should have said that. Then, even if you are not motivated to approach the MinGW developers to effect such changes, someone else (e.g. me) could have.
