Hi, Andrew I can understand the requirement of linking with the newer version GCC to provide the dbase symbol. I'm just trying to understand how EH will work when some objects have EH with absolute references in the data section and some have relative references in the text section. I guess the information is completely local to the object and only has to be self-consistent within the object.
I want to make sure that there are no additional problems of a throw() passing through objects that change the location of the EH information. Thanks, David On Tue, Sep 16, 2014 at 5:04 PM, Andrew Dixie <andrewdixi...@gmail.com> wrote: > 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....@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.
