public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bartoldeman at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103023] ICE (Segmentation fault) with !$OMP DECLARE SIMD(func) linear(ref(u)) Date: Mon, 01 Nov 2021 17:28:04 +0000 [thread overview] Message-ID: <bug-103023-4-IfaDsVhIe4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103023-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103023 --- Comment #2 from bartoldeman at users dot sourceforge.net --- Yes this is about the ICE mainly. It was stripped down from this, which HAS uniform. subroutine func(u,f,ndim) !$OMP DECLARE SIMD(func) uniform(ndim) linear(ref(f,u):1) integer, intent(in) :: ndim double precision, intent(in) :: u(ndim) double precision, intent(out) :: f(ndim) f(1) = u(1) + u(2) f(2) = u(1) - u(2) end subroutine func subroutine main(u,f) double precision, intent(in) :: u(8) double precision, intent(out) :: f(8) !$OMP SIMD do i=1,8,2 call func(u(i),f(i),2) enddo end subroutine main If I leave out ndim and hardcode "2" in func (:: u(2) and :: f(2)), or let the auto-vectorizer and inliner do its work this produces good code (though it would be better with u and f transposed, as basically the code transposes it to two ymm registers in the asm output. With general "ndim" that could still work, e.g. with ndim=3 and 3 equations for u(1:3) -> f(1:3), you'd work with 3 vector registers. Now you may wonder why "ndim" here, since we know it's "2": this comes from feeding a user-defined function into a larger program (that processes e.g. maps) where that same user needs to specify ndim as a parameter. Intel (ifort) doesn't like this at all from what I can see: openfun.f90(1): error #6080: Only scalar variables may be referenced in a LINEAR or MONOTONIC clause. [U] subroutine func(u,f) ----------------^ openfun.f90(1): error #6080: Only scalar variables may be referenced in a LINEAR or MONOTONIC clause. [F] subroutine func(u,f) ------------------^ compilation aborted for openfun.f90 (code 1)
prev parent reply other threads:[~2021-11-01 17:28 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-01 12:34 [Bug fortran/103023] New: " bartoldeman at users dot sourceforge.net 2021-11-01 13:18 ` [Bug fortran/103023] " jakub at gcc dot gnu.org 2021-11-01 17:28 ` bartoldeman at users dot sourceforge.net [this message]
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-103023-4-IfaDsVhIe4@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).