Re: [Mingw-users] status of the gcc 4.3.0 port

[Earnie B. <ea...@us...>]

Quoting Charles Wilson <cwi...@us...>:

> 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 distributing
> "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.

> undoubtedly be issues with 27 different copies of libgcc_s-sjlj-1.dll
> 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.)
>

Libgcc.dll would suffer if it uses a hardcoded shared memory region 
name but I doubt that it does.  I resolved executing more than one 
version of MSYS by using the path to the msys-1.0.dll to create a hash 
for the shared memory region name.

Earnie