public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40472] Simplification of spread intrinsic takes a long time
Date: Fri, 04 Dec 2009 22:40:00 -0000 [thread overview]
Message-ID: <20091204224027.15344.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40472-17820@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from dfranke at gcc dot gnu dot org 2009-12-04 22:40 -------
(In reply to comment #19)
> > Changing to NEW as it (unfortunately) still is.
>
> Are you sure?
Pretty sure. I haven't checked the sources in a while, but I doubt that anyone
got rid of the linear lists (see comment #1). That it "works" now is due to
Paul's patch that rejects simplifications that would result in constructors too
large to handle (by linked lists):
+ if (mpz_get_si (size)*ncopies > gfc_option.flag_max_array_constructor)
+ return NULL;
(see comment #7)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40472
next prev parent reply other threads:[~2009-12-04 22:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 8:31 [Bug fortran/40472] New: Problem with spread intrinsic philippe dot marguinaud at meteo dot fr
2009-06-17 9:19 ` [Bug fortran/40472] " dfranke at gcc dot gnu dot org
2009-06-17 12:58 ` dominiq at lps dot ens dot fr
2009-06-20 9:51 ` [Bug fortran/40472] Simplification of spread intrinsic takes a long time dfranke at gcc dot gnu dot org
2009-06-20 9:58 ` pault at gcc dot gnu dot org
2009-06-20 10:01 ` pault at gcc dot gnu dot org
2009-06-20 12:01 ` dfranke at gcc dot gnu dot org
2009-06-22 4:40 ` pault at gcc dot gnu dot org
2009-06-22 4:48 ` pault at gcc dot gnu dot org
2009-06-22 9:04 ` dominiq at lps dot ens dot fr
2009-06-22 11:51 ` burnus at gcc dot gnu dot org
2009-06-22 12:57 ` dominiq at lps dot ens dot fr
2009-06-22 14:21 ` burnus at gcc dot gnu dot org
2009-06-22 14:33 ` burnus at gcc dot gnu dot org
2009-06-22 19:50 ` dominiq at lps dot ens dot fr
2009-06-22 20:02 ` pault at gcc dot gnu dot org
2009-06-22 20:24 ` burnus at gcc dot gnu dot org
2009-07-10 11:38 ` pault at gcc dot gnu dot org
2009-12-04 22:25 ` dfranke at gcc dot gnu dot org
2009-12-04 22:35 ` dominiq at lps dot ens dot fr
2009-12-04 22:40 ` dfranke at gcc dot gnu dot org [this message]
2009-12-04 22:48 ` dominiq at lps dot ens dot fr
2010-01-02 11:49 ` dominiq at lps dot ens dot fr
2010-05-01 11:15 ` dfranke at gcc dot gnu dot org
2010-05-01 12:15 ` dominiq at lps dot ens dot fr
2010-05-01 12:28 ` dfranke at gcc dot gnu dot org
2010-05-01 12:52 ` dominiq at lps dot ens dot fr
2010-05-01 13:08 ` dfranke at gcc dot gnu dot org
2010-05-01 14:37 ` jvdelisle at gcc dot gnu dot org
2010-05-01 14:53 ` dfranke at gcc dot gnu dot org
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=20091204224027.15344.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).