public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44646] New: [F2008] Implement DO CONCURRENT Date: Wed, 23 Jun 2010 14:01:00 -0000 [thread overview] Message-ID: <bug-44646-13404@http.gcc.gnu.org/bugzilla/> (raw) DO [,] CONCURRENT forall-header is a special loop variant with some extra constraints; in particular, it allows the compiler to run through the loop in any index order. That's somewhat similar to FORALL (or at least to how FORALL is perceived) but avoids (a) temporaries (which FORALL often requires), (b) is no assignment feature (like FORALL) but a real loop, which allows for more things in the loop. First step is to implement the syntax and map DO CONCURRENT on a normal loop; I have a embryonic patch for this. Next step is to optimize for DO CONCURRENT (possibly thinking of automatic parallelization during -fopenmp/-ftree-parallelize-loops, etc.) Interpretation requests (main reason for opening this PR): http://j3-fortran.org/doc/meeting/192/10-172.txt http://j3-fortran.org/doc/meeting/192/10-173.txt http://j3-fortran.org/doc/meeting/192/10-175.txt http://j3-fortran.org/doc/meeting/192/10-176.txt -- Summary: [F2008] Implement DO CONCURRENT Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44646
next reply other threads:[~2010-06-23 14:01 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-23 14:01 burnus at gcc dot gnu dot org [this message] 2010-06-23 20:43 ` [Bug fortran/44646] " tkoenig 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=bug-44646-13404@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).