public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50564] [4.7 Regression] Front-end optimization - ICE with FORALL Date: Sat, 08 Oct 2011 21:41:00 -0000 [thread overview] Message-ID: <bug-50564-4-Ek1EQiNZy1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50564-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50564 --- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2011-10-08 21:41:11 UTC --- FORALL sucks rocks through a straw. We cannot use the usual front-end optimization within forall, because forall(iTime=1:2) tmp = dble(iTime) timeSteps(iTime)=ratio**(tmp-0.5d0)-ratio**(tmp-1.5d0) end forall doesn't work (gfortran correctly warns about multiple assignments to tmp). So, the best method is to disable front-end optimization within a forall loop. I assume the same holds for DO CONCURRENT.
next prev parent reply other threads:[~2011-10-08 21:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-29 8:21 [Bug fortran/50564] New: " burnus at gcc dot gnu.org 2011-09-29 8:35 ` [Bug fortran/50564] " burnus at gcc dot gnu.org 2011-09-29 13:10 ` burnus at gcc dot gnu.org 2011-09-30 6:01 ` tkoenig at gcc dot gnu.org 2011-09-30 9:30 ` burnus at gcc dot gnu.org 2011-10-08 9:31 ` tkoenig at gcc dot gnu.org 2011-10-08 21:41 ` tkoenig at gcc dot gnu.org [this message] 2011-10-09 16:01 ` burnus at gcc dot gnu.org 2011-10-09 16:15 ` burnus at gcc dot gnu.org 2011-10-09 18:11 ` tkoenig at netcologne dot de 2011-10-10 9:24 ` burnus at gcc dot gnu.org 2011-10-10 14:28 ` rguenth at gcc dot gnu.org 2011-10-10 18:57 ` tkoenig at netcologne dot de 2011-10-10 19:09 ` tkoenig at gcc dot gnu.org 2011-10-10 19:15 ` tkoenig at gcc dot gnu.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=bug-50564-4-Ek1EQiNZy1@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).