This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Target specific ABI tweaks
- From: "B. Kosnik" <bkoz at nabi dot net>
- To: libstdc++ at gcc dot gnu dot org
- Cc: paul at codesourcery dot co
- Date: Wed, 23 Jun 2004 09:39:47 -0500
- Subject: Re: Target specific ABI tweaks
- References: <200406231518.56561.paul@codesourcery.com>
>I'm trying to implement the arm C++ EABI. Some of these require changes to
>libstdc++. In particular guard variables and array cookies have a different
>format. We also have several additional EABI specified routines that need
>adding to libsupc++.
I was under the impression that 3.4/3.5 releases were going to keep the
same ABI. If this is not the case (and I believe arm on mainline has
already broken this assumption so perhaps this assumption is already
invalid), I'd appreciate it if you'd explain, in detail, what the ABI
changes are.
Hopefully this change will then be documented in the release notes.
I suggest posting your proposed changes. Some things, like the new
symbols in libsupc++, can easily be handled.
>What would be the preferred way to make these changes? I can't see any
>existing mechanisms for describing target differences from the generic C++
>abi.
I believe Phil Edwards, anticipating this day, already did the work for
target-specific linkage maps. You might want to ask him for suggestions.
-benjamin