On Monday 10 November 2003 5:39 pm, Richard Earnshaw wrote:
[...]
> Having a libgcc_pic is not necessarily wrong.  However, having libgcc_pic 
> that defines those functions that access writable private static data is 
> wrong.  In other words, libgcc_pic != libgcc built as pic; it must be a 
> subset of it.

Right. I guess there were two ways to fix EH. The easy way was to stop linking 
in libgcc_pic as built by gnu/lib/libgcc3. The hard one, which I've been 
looking at when I have time, is to do libgcc{,_eh,_so} properly.

Nick