From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrey Slepuhin <pooh@msu.net>
To: law@cygnus.com
Cc: dje@watson.ibm.com, egcs@cygnus.com
Subject: libgcc problems
Date: Fri, 16 Jan 1998 20:09:00 -0000
Message-id: <XFMail.980117020106.pooh@msu.net>
X-SW-Source: 1998-01/msg00552.html

Hi,

To finalize a discussion about multiple instances of static
variables in libgcc.a (and while egcs-980115 is bootstrapped :-)),
I want to obtain *precise* answers to the following questions:

1) Should we enable by default run-time linking for AIX 4.2 and later?
2) Should we make a patch to move all libgcc's static variables
   into separate shared module for AIX? If yes, I can prepare
   such patch - this is not difficult and needs only few
   changes (I'm already have 80% of such patch).
3) If 1)-2) unacceptable, should we try to do some dirty hack to solve
   a problem with the following method: using pointers to variables
   instead of variables itself in libgcc, and initializing these
   pointers when program starts. This is possible in principle,
   but needs some additional code to be automatically generated
   by collect2, and some changes in libgcc.
4) If 1)-3) is unacceptable I'll treat egcs's exception handling
   on AIX broken.
5) Should we hope that a problem with correct TOC restoring will be
   fixed?

Regards,
Andrey.

P.S. It seems there is a bug in egcs-980115 calls.c because of #ifdef
usage inside a macro. Below there is a possible patch.