public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Dixie <andrewdixie50@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Move unwind info to read-only section on AIX
Date: Tue, 16 Sep 2014 21:04:00 -0000	[thread overview]
Message-ID: <CAPrih1=p0RbvKdn7OVkLBUu8q79ORW8KFmConaknLBZV8HMzFw@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnyn-QHwWU-9dghnRaHKxBhkSLzSiKW06kWRP+G9V_a2j5g@mail.gmail.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.

  reply	other threads:[~2014-09-16 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 21:33 Andrew Dixie
2014-07-31  2:50 ` David Edelsohn
2014-07-31  3:10   ` Andrew Dixie
2014-09-12  0:12 ` Andrew Dixie
2014-09-16 18:37   ` David Edelsohn
2014-09-16 21:04     ` Andrew Dixie [this message]
2014-09-16 21:09       ` David Edelsohn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPrih1=p0RbvKdn7OVkLBUu8q79ORW8KFmConaknLBZV8HMzFw@mail.gmail.com' \
    --to=andrewdixie50@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).