From: Tobias Burnus <burnus@net-b.de>
To: Michael Matz <matz@suse.de>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Implement stack arrays even for unknown sizes
Date: Thu, 14 Apr 2011 20:30:00 -0000 [thread overview]
Message-ID: <4DA75534.4000706@net-b.de> (raw)
In-Reply-To: <4DA75102.2080500@net-b.de>
Tobias Burnus wrote:
> no stack-arrays with stack-arrays
> + -fwhole-program -flto: 10.1s 8.9s
> + -fwhole-program -flto -finline-limit=600 4.8s 3.6s
I wonder whether the following is special to my system* or generally
true. I use:
gfortran -O3 -march=native -ffast-math -funroll-loops -fwhole-program
-finline-limit=600 fatigue.f90
no stack-arrays with stack-arrays
0m6.622s 0m8.174s
-flto 0m8.444s 0m8.174s
Thus, the non "-flto" version is faster (in particular without stack
arrays). I assume that it has to do with the declaration issues of the
front end. However, the last time I tried to find the problem, I failed
to spot anything which looked wrong - especially, the UIDs seemed to be
OK. (Besides, I would like to have the -fno-lto performance also with
.-flto ... ;-)
Tobias
* AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2.4 GHz), x86-64 Linux
next prev parent reply other threads:[~2011-04-14 20:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 10:08 Dominique Dhumieres
2011-04-09 12:17 ` Paul Richard Thomas
2011-04-10 13:29 ` Dominique Dhumieres
2011-04-11 11:49 ` Michael Matz
2011-04-11 11:58 ` Axel Freyn
2011-04-11 13:35 ` Eric Botcazou
2011-04-11 14:06 ` Dominique Dhumieres
2011-04-11 14:59 ` Michael Matz
2011-04-11 16:04 ` Michael Matz
2011-04-11 16:45 ` Steven Bosscher
2011-04-12 11:54 ` Michael Matz
2011-04-12 12:42 ` N.M. Maclaren
2011-04-11 16:46 ` Dominique Dhumieres
2011-04-11 16:59 ` H.J. Lu
2011-04-11 17:06 ` N.M. Maclaren
2011-04-11 18:28 ` Tobias Burnus
2011-04-11 21:18 ` Dominique Dhumieres
2011-04-12 6:23 ` Paul Richard Thomas
2011-04-12 6:35 ` Dominique Dhumieres
2011-04-13 9:42 ` Paul Richard Thomas
2011-04-13 10:38 ` Richard Guenther
2011-04-13 11:13 ` Richard Guenther
2011-04-14 13:32 ` Dominique Dhumieres
2011-04-13 13:46 ` Paul Richard Thomas
2011-04-14 13:59 ` Michael Matz
2011-04-14 15:28 ` Michael Matz
2011-04-14 19:29 ` Dominique Dhumieres
2011-04-15 2:01 ` Dominique Dhumieres
2011-04-15 12:38 ` Michael Matz
2011-04-15 14:06 ` Dominique Dhumieres
2011-04-15 15:19 ` Michael Matz
2011-04-15 15:26 ` Jerry DeLisle
2011-04-15 22:41 ` Michael Matz
2011-04-14 20:23 ` Tobias Burnus
2011-04-14 20:30 ` Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-08 21:29 Michael Matz
2011-04-09 8:21 ` N.M. Maclaren
2011-04-09 8:51 ` Magnus Fromreide
2011-04-09 9:02 ` Eric Botcazou
2011-04-09 9:49 ` N.M. Maclaren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA75534.4000706@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=matz@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).