> dannysmith-g wrote:
> > GCC 4.2.0 has been released.
> > What would mingw users like for a binary release package?
> > (1) Based on pristine (well, just a few makefile.in tweaks
> to get around
> > CRLF, no-symlinks, etc issues) FSF sources, as is, with known bugs.
> I'm going to go out on a limb and say "1". It has been three entire
> /long/ development cycles -- to 4.0, to 4.1, and now to 4.2 -- since
> mingw had a "current" version of gcc; I don't think any of us want to
> see that kind of lag-behind happen again.
Actually, that's not the way it works. Everbody have been and are free
to have a current version of gcc built for mingw. Or they could pay
someone else to build and support it for them. I believe CodeSourcery
has provided such support. I provide such support (w/ or w/o bells and
whistles) to a few people.
> Just a side note: even though DW2 unwind is faster, better, and more
> widely used (and thus more widely tested) than sjlj, IMO mingw should
> still supply a sjlj compiler, at least as an alternate
> download -- until
> the foreign frame problem is solved:
> "DW2 EH is supported for Windows, but someone needs to implement the
> part that makes it possible for GUI callbacks to throw
> exceptions that
> can be caught in the main event loop, i.e. make exception-propagation
> work through "foreign" call frames in the stack.
> If I understand correctly, ^^^ is predicated on having shared
> libgcc --
> hence the exception-to-the-rule in Chuck's world.
That is a misunderstanding. Shared libgcc is not necessary.
Also, there are workarounds, eg raisng OS exceptions and catching with a
frame state fallback mechanism
> I can deal with a slightly less capable 4.2.x on mingw -- and simply
> wait another six months or so for 4.3.0, in which all these
> spiffy new
> things will be integrated into the official GNU release (we
> all hope --
> since we'll all be working feverishly on gcc trunk
Yeah. Whose world is that?