public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84991] [openacc] Misleading error message for function static var in routine
Date: Fri, 09 Apr 2021 16:06:17 +0000 [thread overview]
Message-ID: <bug-84991-4-02QQqRR0dr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84991-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84991
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org
See Also| |https://github.com/OpenACC/
| |openacc-spec/issues/372
Status|UNCONFIRMED |SUSPENDED
Last reconfirmed| |2021-04-09
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> The openacc spec tells us at 2.15.1. Routine Directive:
> ...
> In C and C++, function static variables are not supported in functions to
> which a routine directive applies.
> ...
>
> When compiling such an example with -fopenacc:
> [...]
... this now works as expected.
Current behavior documented via commit ffa0ae6eeef3ad15d3f288283e4c477193052f1a
"Add 'libgomp.oacc-c-c++-common/static-variable-1.c' [PR84991, PR84992,
PR90779]".
See <http://mid.mail-archive.com/87r1jjxxk7.fsf@euler.schwinge.homeip.net>;
waiting for OpenACC specification, thus setting "suspended" here.
prev parent reply other threads:[~2021-04-09 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-84991-4@http.gcc.gnu.org/bugzilla/>
2021-04-09 15:29 ` cvs-commit at gcc dot gnu.org
2021-04-09 15:31 ` cvs-commit at gcc dot gnu.org
2021-04-09 16:06 ` tschwinge at gcc dot gnu.org [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-84991-4-02QQqRR0dr@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).