[MinGW-dvlpr] Are we ready for 3.3?

[Danny S. <dan...@cl...>]

Hi,
I'm satisfied with my builds and regtests of gcc-3.3 with  infamous
mingw-local patches (some still cooking) and I wonder if we should try
it out on user base.

Cooking are the patches I submited for 3.4 (and one  -- re C++ multiple
inheritance vs dllimport -- which I will submit after I get feedback on
the first lot). These are mainly a reworking of Mumit Khan ex Doug Evans
ex who-knows patches. They do not fix the friend declaration bug nor
some dllexport-inline-function bugs.  There are workarounds though.

The patches I submitted replace ICE with either warnings about ambiguous
syntax that I resolve in favour of getting things to still work rather
than MSVC rules) or hard errors for really stupid syntax like
"__declspec(dllexport) static void  foo();"

I'v e native bootstrapped  the lot (all languages and lib, with the
exception of boehm-gc enabled libobjc.a) and regtested, but that doesn't
mean a lot for dll's because there are't many dll cases in the
testsuite.

Okay. I'm willing to upload C, C++, Objc, fortran, Ada binaries.  Java
runtime libs are very big and my ISP can be flakey at time, so I'm
hoping some one else will do Java, but I can do if know else wants to.

How do you want to split up the big big package:

Ranjit, Embar.-- I needed to do one additional change for native build
of libjava -- change the use of ':' as a path separator in  libjava
makefile to $(PATH_SEPARATOR).  I've hacked this for now, but need to
work on a real fix.  The libjava configure.in  doesn't play nice with my
default version of autoconf (2.53) so I'll have to wait till I have some
free time to fix properly.  Golly there are a lot of warnings in
building libjava -- are they all harmless?

Danny