> From: Earnie Boyd>
> Quoting Charles Wilson <cwilso11@...>:
> > My advice: after sufficient discussion, the mingw project
> has three choices:
> > a) "if you want working exception handling, use -shared-libgcc"
> > b) Find Aaron, KT(?), and VR(?) and convince them to continue --
> > or at least publish -- their work/discussions/ideas about this,
> > and git-er-done.
> > c) Officially adopt Danny's disavowed patch as ported by tdragon,
> > and accept that ABI as "the" ABI for mingw.
> > Me, I'd lean towards (a) but mingw users seem allergic to
> > "extra" DLLs (c.f. whining about mingwm10.dll). Also, there will
> My choice would be (a) as well. We'd end up with on package that
> distributes just the libgcc.dll and mingwm10.dll. Then the
> distributors can point users to that package if they don't want to
> carry the source for them.
a) by itself is not sufficient. libstdc++_[dw2|sjlj]-6.dll is also required for support
of c++ EH across dll boundaries. Likewise libobjc_[dw2|sjlj] need to be dll.
Ditto libgnat_[dw2|sjlj], libjava_[dw2|sjlj]. So it would avoid a lot of pain for both
users and maintainers if mingw decided to go with with either DW2 (like cygwin, by
preference) or stick with sjlj (like mingw64, by necessity)
> > undoubtedly be issues with 27 different copies of
> > floating around on the same system -- unless we are very
> careful about
> > ABI compatibility. (Does libgcc suffer from the "you can't have more
> > than one of me installed" problems that cygwin1.dll does? I
> don't think
> > so --- but I'm not sure.)
No, libgcc doesn't suffer directly from multiple copies but it will indirectly by the
confusion and maintenance burden.