Re: Target specific ABI tweaks

[Paul Brook <paul at codesourcery dot com>]

On Wednesday 23 June 2004 15:47, B. Kosnik wrote:
> (wrong cc on this, resending)
>
> >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.

http://www.armdevzone.com/EABI/cppabi.pdf
I expect 2.7, 2.8, 3.3.2 and maybe 3.1.5 to need changes in libstdc++.

I'm not aware of any mainline ABI changes so far on mainline. We've added a 
new ABI, but the old one should still work. As a parallel change we're also 
switching from sjlj exceptions to eabi based unwind tables.

> 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.

Ok. I guess I can just use #ifdef __arm__ initially, then reconsider once we 
have more idea exactly what is involved.

Paul