> The merge is done and the trunk is open again under the usual
> stage1 rules.
Don't forget to update svn.html. ;-)
Cheers, Ben
Richard,
Thanks for the clarification. So we ought to see some improvements
in the compile time of the polyhedron benchmarks by tomorrow...
http://users.physik.fu-berlin.de/~tburnus/gcc-trunk/benchmark/
The graphite merge should provide some performance improvement
regarding loop optimization
On Mon, 28 Jul 2008, Jack Howarth wrote:
> Richard,
>Is there any information on what sort of performance improvements
> we might see from the tuples merge? Or would those require additional
> merges like graphite?
The tuples is supposed to reduce the memory footprint of our tree IL
and as a
Richard,
Is there any information on what sort of performance improvements
we might see from the tuples merge? Or would those require additional
merges like graphite?
Jack
On Mon, Jul 28, 2008 at 04:42:26PM +0200, Richard Guenther wrote:
> On Sun, 27 Jul 2008, Richard Guenther wrot
On Sun, 27 Jul 2008, Richard Guenther wrote:
> The trunk is frozen now until after the merge of the tuples branch
> which will happen tomorrow, Monday Jul 28th. Unfreezing of the
> trunk will be annonced after the fact.
The merge is done and the trunk is open again under the usual
stage1 rules.
The trunk is frozen now until after the merge of the tuples branch
which will happen tomorrow, Monday Jul 28th. Unfreezing of the
trunk will be annonced after the fact.
Thanks,
Richard.
--
Richard Guenther <[EMAIL PROTECTED]>
Novell / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernbe
