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/46532] [OMP] missing error for loop bounds missing an attribute
Date: Thu, 18 Nov 2010 12:58:00 -0000 [thread overview]
Message-ID: <bug-46532-4-y3iFBgqvxe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46532-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46532
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid, openmp
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.11.18 12:56:26
CC| |burnus at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-11-18 12:56:26 UTC ---
Intel has:
error #6752: Since the OpenMP DEFAULT(NONE) clause applies, the PRIVATE,
SHARED, REDUCTION, FIRSTPRIVATE, or LASTPRIVATE attribute must be explicitly
specified for every variable. [N]
>From the OpenMP 3.0 specification:
"The default(none) clause requires that each variable that is referenced in the
construct, and that does not have a predetermined data-sharing attribute, must
have its data-sharing attribute explicitly determined by being listed in a
data-sharing attribute clause." ("2.9.3.1 default clause")
Cf. also "2.9.1.1 Data-sharing Attribute Rules for Variables Referenced in a
Construct", which lists the variables which have "predetermined data-sharing
attributes"; in the example, it only affects "i" ("The loop iteration
variable(s) in the associated do-loop(s) of a do or parallel do construct
is(are) private.")
next prev parent reply other threads:[~2010-11-18 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 6:21 [Bug fortran/46532] New: " Joost.VandeVondele at pci dot uzh.ch
2010-11-18 12:58 ` burnus at gcc dot gnu.org [this message]
2012-06-29 18:46 ` [Bug fortran/46532] " Joost.VandeVondele at mat dot ethz.ch
2023-04-08 18:53 ` anlauf 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-46532-4-y3iFBgqvxe@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).