My proposal for the libgcc runtime ABI (ia64 gcc/glibc is broken.)

[Martin v. Loewis]

> Is there something really wrong with just sidestepping this issue
> altogether with the following simple rule:
> 
>  - libgcc is always statically linked inside the object file that needs
>    it (be it a binary or a shared library)
> 
> Yes. It will result in code duplication. Is that a huge problem?

The problem, in the past, was that there are also multiple copies of
static variables in the process. That was a huge problem, as some
function would put data into one variable, and another function would
expect it in another variable.

Regards,
Martin