This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Readiness of tree-ssa


On Tue, 2004-01-20 at 14:48, Wolfgang Bangerth wrote:
> Just as another datapoint: we've got a number of people routinely compiling 
> and running applications nightly. Off the top of my head, this would be 
> Gerald, Guenther (POOMA), and me, and I'm certainly missing more. As far as I 
> can see none of us has had much success with tree-ssa yet. 
> 
We've been building DLV nightly and it seems to work.  The last build
was on Jan/17.  Has it broken since then?

We're having some problems building POOMA, though they seem
configuration related.  Brian, have you had any luck with it?

> I understand and appreciate that the tree-ssa people are putting a significant 
> amount of work into the branch. However, I'd like to propose postponing the 
> merge until at least the testers inside the gcc project are reasonably happy 
> with the branch. Whatever they will find, we'll get as reports later anyway, 
> but this way we could make sure that it's fixed before it propagates to the 
> mainline.
> 
Is there a PR for the problems you're having with your code?  I'd like
to have PRs for all the major problems people are seeing with the
branch.  We could then have a blocker PR that depends on all of those
that we agree should be addressed before the merge or immediately after
the merge.

Let's face it, when we merge the branch, we expect to have some amount
of fixing work to do.  We can't pretend that the code will be releasable
by then.  But we need to make sure that we merge in a state where the
problems are manageable.


Thanks.  Diego.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]