Danny Smith wrote:
> Since release of gcc 3.2.1 and my upload of 3.2.1 ming binaries, there
> have been numerous (>35) fixes to close PR's on 3.2 branch. There is
> one significant _alloca vs -fomit-frame-pointer cygwin/mingw
> optimisation bug on 3.2 (and 3.3. and 3.4) that I am interested in
> (patch submitted, but unreviewed --'hum,hum', said the old Ent).
> Given that, should I move my RC to release status, or just wait for 3.3
> which is wonderful and due for release in Feb. probably near time of
> 3.2.2 release.
Good question. I was going to ask the same, given your recent release
of binutils. I think moving the 3.2.1 out of RC to release status would
be a good thing at the time you move your latest binutils to release
status. I'll then give new releases to w32api and mingw-runtime
individual packages and roll out a new installation binary.
One thing I'm not sure of, is it necessary to rebuild all objects with
sjlj or can dwarf2 objects mix with sjlj?
> I want to spend time in 3.4 which is even more wonderful, and would
> like to forget about 3.2.1/3.2.2 for awhile.
> Is this confusing? You bet it is. I don't wish to add confusion to
> mingw users, some of whom apparently think that gcc-2.95-5 is shiny, so
> I seek advice.
And some still play around with their Tandy Radio Shack 80 computers as
well. ;) As the GCC bugs stabilize more and more will give up 2.95. I
still see references to EGCS and how long ago did 2.95 appear?