Re: [arm-gcc] state of the csl-arm-branch

[Paul Brook <paul@xxxxxxxxxxxxxxxx>]

On Friday 18 June 2004 09:50, Matthias Klose wrote:
> Hi,
>
> taken this address from the version.c file, CCing Zack as I know he's
> using sometimes a Debian dist for work.
>
> At Debconf4 just before the GCC summit, we (Debian) tried to evaluate
> our upgrade options to newer toolchain components for releases after
> sarge.  One issue was gcc-3.4 -> gcc-3.5 ABI stability.  AFAIK it's
> planned to remain stable, but maybe not for arm-linux, when/if the
> csl-arm-branch is integrated into mainline before the creation of the
> gcc-3.5 branch.  Surely we would like to keep the arm ABI stable as
> well between these two releases (Debian transitions take a long time),
> so questions go in the direction how this can be done.  The
> csl-arm-branch currently tracks the gcc-3.4 branch.  Is there an
> estimated date for merging the csl-arm-branch?  Is the csl-arm-branch
> stable enough to base a system default compiler on it?  gcc-3.4 isn't
> yet part of a Debian "release", not yet in unstable, so we would bot
> have the pain of a 3.4 -> 3.4-csl transition.

The csl-arm branch has already been merged into mainline (will be 3.5). We are 
continuing to maintaining the csl-arm-branch (tracking 3.4) in parallel with 
mainline as a base for our releases.

We have no plans to merge the csl-arm-branch into the 3.4 branch.

In the next few months we expect to be making changes to the c++ ABI in line 
with the arm eabi. These changes will be made to both mainline and 
csl-arm-branch (but not 3.4).

The C abi should remain stable. However csl-arm and 3.5 will also support the 
arm eabi. Some parts of this are already implemented, others are still in 
progress (as mentioned above).

Paul