6.0 issues

6.0 issues

[Andrew Cagney]

Off the top of my head:

- the gdb.cp re-vamp scheduled for near the end of this week
- red zone re-fix

And I guess:

- something about GDB vs GCC over unknown CFI register values

New features shouldn't be going into the 6.0 branch (although there is 
an extreem tollerance towards targets getting their frame code rewritten 
:-).

Andrew

Re: 6.0 issues

[David Carlton]

On Mon, 18 Aug 2003 11:53:18 -0400, Andrew Cagney <ac131313@redhat.com> said:

> Off the top of my head:
> - the gdb.cp re-vamp scheduled for near the end of this week
> - red zone re-fix

> And I guess:

> - something about GDB vs GCC over unknown CFI register values

I been happier if the Java bug were fixed; having said that, the bug
was also present in 5.3, albeit for different reasons, so I suppose it
shouldn't be a show-stopper.  But there was a few months in the middle
where Java debugging worked better than it did in 5.3 or does
currently.

David Carlton
carlton@kealia.com

Re: 6.0 issues

[Andrew Cagney]

Just to re-iterate a point: GDB's releases are time rather than feature 
based.

- in the past attempts to do feature based releases have gone badly off 
the rails.  This 6.0 release had some annotate related features and it, 
consistent with the form, has also suffered schedule problems

- the general intent is, once the branch has been cut, only fixes get 
pushed onto it.  The late completion of the annotate stuff has blured 
this, as has the frame stuff, but the general intent is still there.

New features go into the mainline, and people wanting the features can 
pick it up from there.

Andrew

Re: 6.0 issues

[Andrew Cagney]

> Off the top of my head:
> 
> - the gdb.cp re-vamp scheduled for near the end of this week
> - red zone re-fix
> 
> And I guess:
> 
> - something about GDB vs GCC over unknown CFI register values
> 
> New features shouldn't be going into the 6.0 branch (although there is an extreem tollerance towards targets getting their frame code rewritten :-).

I should add, I'm thinking of rolling out a draft this weekend 
(2003-08-23), and the final a week later (2003-08-30ish).

Andrew

6.0 release schedule; Was: 6.0 issues

[Andrew Cagney]

> I should add, I'm thinking of rolling out a draft this weekend (2003-08-23), and the final a week later (2003-08-30ish).

In light of some recent follow-fork changes, I'm going to toss in an 
extra week:

2003-08-24-gmt: draft
2003-08-32-gmt: final

Andrew

Re: 6.0 release schedule; Was: 6.0 issues

[H. J. Lu]

On Fri, Aug 22, 2003 at 11:02:05AM -0400, Andrew Cagney wrote:
> 
> >I should add, I'm thinking of rolling out a draft this weekend 
> >(2003-08-23), and the final a week later (2003-08-30ish).
> 
> In light of some recent follow-fork changes, I'm going to toss in an 
> extra week:
> 
> 2003-08-24-gmt: draft
> 2003-08-32-gmt: final

You must be using a different calendar than mine :-).


H.J.

Re: 6.0 release schedule; Was: 6.0 issues

[Andrew Cagney]

> 
> I should add, I'm thinking of rolling out a draft this weekend (2003-08-23), and the final a week later (2003-08-30ish).
> 
> In light of some recent follow-fork changes, I'm going to toss in an extra week:
> 
> 2003-08-24-gmt: draft
> 2003-08-32-gmt: final

Doh!  2003-09-07-gmt ish

> 
> Andrew
> 
> 
>