This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH] Fix PR34706, PR34683 -- use more precise types for fortran arrays
- From: "Janus Weil" <jaydub66 at googlemail dot com>
- To: "Richard Guenther" <rguenther at suse dot de>
- Cc: gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Tue, 8 Jan 2008 22:03:14 +0100
- Subject: Re: [PATCH] Fix PR34706, PR34683 -- use more precise types for fortran arrays
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Srxsg3RrhGfnLLxGa51ev717GOkHY8uzO+aZX1RBUuA=; b=ez/CSHkoTUrvxGdMYOnZ3tSpGu+gvIF69wtFXC8+wW+Kd+9sWozhBBQrY06MynWI8VXQ1OItYZEA02VOLMRtnJljGZC2LXI7hAVqKlBgfJwHuqx1vNwqfNwkxz/r75sOd+WrAhbNXNYz2eZCwLPhPPu6mWs5tFxSCGgzqpiG1Nw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Na2F7s6wIXqJ7tIZUh9gHeAKQ0nEL9kVS4R4tPRVZzFnxk+ITPdA9ZdfwaldVy6fD4JTMLeJufDXVtks09x5eu8F+TIhGhzkuRROD6s0zWEIMr+ktM96nJcSHUvmMt5+R70UqpRajhvHJ22zJOiFL05mW96HKaeAXJSbl0uFLd8=
- References: <Pine.LNX.4.64.0801081143240.3891@zhemvz.fhfr.qr> <854832d40801081253m5bf0a52n2d53253441943598@mail.gmail.com>
Btw, with 131401 and your patch, compiling with -O3 uses even less
memory than -O1 -fstrict-aliasing (only 390MB, most of the stuff in
"tree operand scan" went away), but it's slower (51 sec).
While -O2 is worse (97sec, 670MB).
2008/1/8, Janus Weil <jaydub66@googlemail.com>:
> Hi Richard,
> thanks for taking care of this. Already the other patches you
> committed in connection with PR34683 have helped a bit. With rev.
> 131401 the test case compiles in about 60sec using 570MB of memory
> (with -O1 -fstrict aliasing). This is already significantly better
> than the 800MB from before.
> After applying your trans-types.c patch, this further improves to
> 33sec and 440MB. Which is nice, but still way above last years'
> October builds. Most of the memory is still used for "tree operand
> scan" and "tree FRE". So I guess there still must be something going
> wrong.
> But I think this patch is fine.
> Cheers,
> Janus