public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19925] Implied do-loop in an initialization expression is broken
Date: Fri, 01 Feb 2008 16:42:00 -0000	[thread overview]
Message-ID: <20080201164118.17515.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19925-8446@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from dominiq at lps dot ens dot fr  2008-02-01 16:41 -------
For large values of n, most of the time is spent in gfc_append_constructor,
starting from 5% and up to 92%.  Most of the remaining time is spent in
find_array_section, starting from 75% down to 2.5%.
Although I did not follow closely the algorithm, I got it is basically
quadratic (for an intrinsically linear problem). Also, each time
gfc_get_constructor is called, there is a call to "gfc_getmem
(sizeof(gfc_constructor))".


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19925


  parent reply	other threads:[~2008-02-01 16:42 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19925-8446@http.gcc.gnu.org/bugzilla/>
2005-11-04  1:19 ` pinskia at gcc dot gnu dot org
2006-01-09 22:33 ` pinskia at gcc dot gnu dot org
2006-01-10  0:03 ` eedelman at gcc dot gnu dot org
2007-01-02 21:48 ` bdtaylo1 at uiuc dot edu
2007-05-09  3:02 ` jvdelisle at gcc dot gnu dot org
2007-10-06 14:09 ` tobi at gcc dot gnu dot org
2007-10-29 15:00 ` jv244 at cam dot ac dot uk
2007-11-26  4:50 ` jvdelisle at gcc dot gnu dot org
2007-11-26  6:28 ` jvdelisle at gcc dot gnu dot org
2007-11-26  6:52 ` jvdelisle at gcc dot gnu dot org
2008-01-08 19:27 ` jvdelisle at gcc dot gnu dot org
2008-01-29  8:57 ` jv244 at cam dot ac dot uk
2008-01-29 15:36 ` Jerry_V_DeLisle at rl dot gov
2008-01-30  7:03 ` jvdelisle at gcc dot gnu dot org
2008-02-01  4:43 ` jvdelisle at gcc dot gnu dot org
2008-02-01 13:40 ` burnus at gcc dot gnu dot org
2008-02-01 15:32 ` dominiq at lps dot ens dot fr
2008-02-01 16:04 ` sgk at troutmask dot apl dot washington dot edu
2008-02-01 16:42 ` dominiq at lps dot ens dot fr [this message]
2008-02-01 17:06 ` dominiq at lps dot ens dot fr
2008-02-02  2:05 ` jvdelisle at gcc dot gnu dot org
2008-02-02 11:10 ` dominiq at lps dot ens dot fr
2008-02-02 16:39 ` sgk at troutmask dot apl dot washington dot edu
2008-09-07  8:27 ` linuxl4 at sohu dot com
2008-09-07 16:35 ` sgk at troutmask dot apl dot washington dot edu
2008-10-11 10:33 ` dominiq at lps dot ens dot fr
2008-11-01 16:45 ` jvdelisle at gcc dot gnu dot org
2008-11-01 17:03 ` jvdelisle at gcc dot gnu dot org
2008-11-01 17:08 ` jvdelisle at gcc dot gnu dot org
2005-02-12 21:10 [Bug fortran/19925] New: " sgk at troutmask dot apl dot washington dot edu
2005-02-12 21:17 ` [Bug fortran/19925] " pinskia at gcc dot gnu dot org
2005-05-14 20:58 ` pinskia at gcc dot gnu dot org
2005-07-28 11:56 ` erik dot edelmann at iki dot fi

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=20080201164118.17515.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).