GDB 6 schedule

[Andrew Cagney]

> Hi Andrew,
> 
> The port consists of a tdep file and a remote back-end over two files (there
> is a lot of code in the remote back-end and two clear levels of
> abstraction).

It possible for the tdep file to just slip into place - the problematic 
interfaces have all now largely been clearly identified.  The remote 
stuff could get a few red flags - with the architecture vector largely 
overhauled the remote stuff could find itself needing core changes.

> The trunk has moved on considerably sinse the last major release and I need
> some of the new features such as reg groups (several hundred registers).
> 
> If there is a concern then I would be happy if a tempory branch of the gdb
> directory was created to work on for the next few weeks prior to merging to
> the trunk, however as you say, the worst that can happen is that the ip2k
> port doesn't work.

I think you'll want to always work on the head.  Once the file is mostly 
ok, it can be added to the mainline.  The configuration changes can be 
added later.

> I would appreciate your help and time to make this work.

Post stuff here and someone should be able to help.

Andrew