Development plan *ducks* (Re: Loop optimizer issues)

[Zdenek Dvorak]

Hello,

> > onto a branch, try to get GCC 3.4 out ASAP (ie. on schedule: ~4 months
> > from now), and take a few extra months for 3.5 (or 4.0? :-).  But we
> > already have too many open bugs, and the intermodule patch is just huge,
> > so this may be just not feasible/reasonable.
> > (BTW How many of the bugs targeted for 3.4 really are regressions?)
> > 
> > Another option is to open a pre-3_5-merge-branch, which would be
> > rtlopt+tree-ssa in their current shapes; all non-3.4 development
> 
> Current rtlopt branch has bit too many of unrelated changes in it
> as some of changes we did in cfg branch didn't get into 3.3, where moved
> to rtlopt-branch and they didn't get into 3.4 too.
> I am thinking about creating 3.4 based branch once 3.4 freezes and move
> relevant bits there together with some cleanups after merge headachaes we
> had on rtlopt branch.

please note that they are not relevant to merging the loop optimizer
part I propose.  The merging of loop optimizer simply involves merging
every change done on rtlopt-branch in last 4 months (as nobody but me
was working there in that time) and fixing the conflicts caused mostly
because of converting old function declaration conventions.

Zdenek