> So ... is there a valid reason for this, or is this just an accident
> of history?  AFICT, this behavior dates back to 2007 as of r120429
> (http://gcc.gnu.org/viewcvs/trunk/libgcc/static-object.mk?view=markup&pathr
>ev=120429).

At least on some platforms, you cannot have more than one libgcc_eh in an 
entire link, otherwise you cannot propagate exceptions across modules.

-- 
Eric Botcazou

Reply via email to