public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49575] OpenMP has a problem with -funroll-loops Date: Wed, 29 Jun 2011 18:41:00 -0000 [thread overview] Message-ID: <bug-49575-4-kW0eUINAfn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49575-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49575 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |openmp CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-29 18:40:42 UTC --- The problem isn't that the loop isn't unrolled, it is unrolled just fine. The problem is that ompexp pass runs too early, no CCP is performed before that, so it isn't able to figure out that k is constant in the loop unless you explicitly say so or unless you declare it in the body of the parallel region. We currently expand omp before SSA, while CCP needs SSA, but not sure what kinds of issues could cause the pass reordering. Alternative to reshuffling the passes would be to do some kind of OpenMP IPA optimization, if constant/gimple invariant values are stored into the omp_data structure, we could modify both the caller not to store them and callees to replace all reads from that with the invariant.
next prev parent reply other threads:[~2011-06-29 18:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-29 9:46 [Bug c++/49575] New: " sailorweb2 at hotmail dot com 2011-06-29 18:41 ` jakub at gcc dot gnu.org [this message] 2011-06-29 19:38 ` [Bug c++/49575] " sailorweb2 at hotmail dot com 2011-06-29 19:50 ` jakub at gcc dot gnu.org 2011-12-16 0:43 ` [Bug middle-end/49575] " pinskia 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-49575-4-kW0eUINAfn@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).