This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Move unwind info to read-only section on AIX
- From: Andrew Dixie <andrewdixie50 at gmail dot com>
- To: David Edelsohn <dje dot gcc at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 17 Sep 2014 09:04:46 +1200
- Subject: Re: Move unwind info to read-only section on AIX
- Authentication-results: sourceware.org; auth=none
- References: <CAPrih1nqm8w0YoCdBv6iuj_56JmvXGSGQFh5rwa3GS3sLrf5hQ at mail dot gmail dot com> <CAPrih1ngHH_bhJz=iSLs3qzWk85fR0MRgD1zsg1_JBXq-SK0SQ at mail dot gmail dot com> <CAGWvnyn-QHwWU-9dghnRaHKxBhkSLzSiKW06kWRP+G9V_a2j5g at mail dot gmail dot com>
Hi David,
On AIX, mixing objects from different GCC versions should work as long
as the newest GCC is used for linking. I tested a library with some
objects compiled by GCC-4.4 and some objects compiled by a patched
GCC-5.0. Exceptions passed through the mixed objects without issue.
Did you have a specific example or reason to think it wouldn't work?
If one attempts to mix C++ objects from GCC-3.3 and GCC-4.4 on Linux
or Solaris there are link time errors. If you're worried about the
risk of runtime problems, would you rather have a deliberate link time
error on AIX?
Regards,
Andrew
On Wed, Sep 17, 2014 at 6:37 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
> My concern is this really is an ABI change. One cannot mix object
> files compiled with the old EH format and with the new EH format. One
> can mix shared libraries of different styles, but not object files.
> I'm not certain how much of a problem it is to require recompiling
> everything from scratch.