public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106566] New: [OpenMP]
Date: Mon, 08 Aug 2022 20:35:31 +0000 [thread overview]
Message-ID: <bug-106566-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106566
Bug ID: 106566
Summary: [OpenMP]
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: openmp, rejects-valid
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
The OpenMP example
https://github.com/OpenMP/Examples/blob/v5.2/SIMD/sources/linear_modifier.1.f90
is rejected as:
13 | !$omp declare simd(add_one2) linear(p: ref) simdlen(8)
| 1
Error: Symbol ‘add_one2’ at (1) has already been host associated
if it is a module procedure. When commenting the 'module ... contains' and 'end
module', it compiles just fine.
(Similar the .2 and .3 in the examples.)
next reply other threads:[~2022-08-08 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 20:35 burnus at gcc dot gnu.org [this message]
2022-08-09 18:28 ` [Bug fortran/106566] [OpenMP] declare simd fails with with bogus "already been host associated" for module procedures burnus at gcc dot gnu.org
2022-08-16 8:16 ` burnus at gcc dot gnu.org
2022-08-16 15:26 ` burnus 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-106566-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: link
Be 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).