mingw32-gcc update

Kalev Lember kalev at smartlink.ee
Tue Aug 25 13:09:36 UTC 2009


Erik van Pienbroek wrote:
> Op dinsdag 25-08-2009 om 12:37 uur [tijdzone +0300], schreef Kalev
> Lember:
>> I'd rather keep our mingw32-gcc package as close to possible to the
>> native gcc package. It would probably better if those patches went
>> through gcc upstream first. Having said that, here's a list of the patches:
> 
> Yeah, I agree that such patches should be upstreamed ASAP. However, I
> think it's best to keep code generated with our mingw32-gcc compatible
> with code generated by mingw.org's gcc as several people are using both
> our toolchain and the mingw.org toolchain.

mingw.org gcc is compiled with --disable-sjlj-exceptions --with-dwarf2,
and that's what mostly makes in incompatible with ours.


>>> gcc-4.4.0-20090615-seh_aware.patch
>> This is a rather large patch (22KB) that adds some new
>> exceptions-related code. Since it's not a bugfix, I think it should go
>> through gcc upstream first. Also such change probably needs a large
>> rebuild of all mingw packages, rendering them binary incompatible with
>> old ones. I'd rather skip this.
> 
> I just searched the GCC bugzilla and the only relevant bug I could find
> is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34684
> It looks like the mingw folks didn't try to upstream this one yet.
> Could you please ask the mingw folks what this patch exactly does and
> when they're going to upstream it?

Looking at the code it's a dwarf exception patch. We are still using the
sjlj exceptions, so right now it doesn't matter for us.

I think changing exception types is something for F-13. Right now we
should just update the toolchain, but I think it's too late in the
release cycle to start changing exception types.

Anyway, I'll ask mingw people if they can get this patch upstream.


-- 
Kalev



More information about the mingw mailing list