This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [v3] Update Solaris baselines for GCC 4.7


Paolo Carlini <paolo.carlini@oracle.com> writes:

> I'm trying to understand why on Solaris you didn't see abi_check errors,
> because for sure on Linux those operators are in the baselines and normally
> exported, isn't just about the linker script. I repeat one last time: on
> Linux we started exporting the symbols @3.4.5, and for real, isn't just
> that the linker script mentioned the symbols. Then, we (or Jakub) updated
> the Linux baselines many times, and the baselines always included those
> symbols. There is nothing special going on on Linux. How you can profitably
> use this information to understand what't going on on Solaris, I don't know
> exactly.

The first gcc release with symbol versioning support was 4.6, and those
symbols are *not* in the 4.6 baselines, consistent across both sparc and
x86.  They only started to appear recently due to the code generation
change I've identified.  I've no idea why this happened, though.

There seem two ways forward:

* Understand why they appear now, caused by Martin's change, and didn't
  before.  Perhaps there's a way to make them `go away'...

* Accomodate them in gnu.ver by exporting them @3.4.17 *for Solaris
  only*.  I can certainly do that, but would rather understand first
  what caused their appearance in the first place to avoid them to
  appear and disappear willy-nilly.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]