public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/66873] New: fortran variant of outer-1.c not parallelized by autopar Date: Tue, 14 Jul 2015 22:39:00 -0000 [thread overview] Message-ID: <bug-66873-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66873 Bug ID: 66873 Summary: fortran variant of outer-1.c not parallelized by autopar Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- Consider this example, a fortran version of autopar/outer-1.c: ... program main implicit none integer, parameter :: n = 500 integer, dimension (0:n-1, 0:n-1) :: x integer :: i, j, ii, jj do ii = 0, n - 1 do jj = 0, n - 1 x(ii, jj) = ii + jj + 3 end do end do do i = 0, n - 1 do j = 0, n - 1 if (x(i, j) .ne. i + j + 3) call abort end do end do end program main ... When trying to parallelize this using -O2 -ftree-parallelize-loops=2, it fails on the dependencies: ... (Data Dep: #(Data Ref: # bb: 4 # stmt: x[_12] = _14; # ref: x[_12]; # base_object: x; # Access function 0: {{0, +, 1}_3, +, 500}_4 #) #(Data Ref: # bb: 4 # stmt: x[_12] = _14; # ref: x[_12]; # base_object: x; # Access function 0: {{0, +, 1}_3, +, 500}_4 #) access_fn_A: {{0, +, 1}_3, +, 500}_4 access_fn_B: {{0, +, 1}_3, +, 500}_4 (subscript iterations_that_access_an_element_twice_in_A: [0] last_conflict: scev_not_known iterations_that_access_an_element_twice_in_B: [0] last_conflict: scev_not_known (Subscript distance: 0 )) inner loop index: 0 loop nest: (3 4 ) distance_vector: 0 0 distance_vector: 500 -1 direction_vector: = = direction_vector: + - ) FAILED: data dependencies exist across iterations ...
next reply other threads:[~2015-07-14 22:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-14 22:39 vries at gcc dot gnu.org [this message] 2015-07-14 22:53 ` [Bug tree-optimization/66873] " vries at gcc dot gnu.org 2015-07-14 23:02 ` vries at gcc dot gnu.org 2015-07-14 23:18 ` vries at gcc dot gnu.org 2015-07-14 23:23 ` vries at gcc dot gnu.org 2015-07-14 23:39 ` kargl at gcc dot gnu.org 2015-07-15 6:12 ` vries at gcc dot gnu.org 2015-07-15 10:01 ` vries at gcc dot gnu.org 2015-07-15 20:29 ` vries at gcc dot gnu.org 2015-07-24 16:56 ` vries at gcc dot gnu.org 2015-07-26 17:12 ` vries at gcc dot gnu.org 2015-07-26 21:39 ` vries 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-66873-4@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).