From: Jakub Jelinek <jakub@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Cesar Philippidis <cesar_philippidis@mentor.com>
Subject: Re: open acc default data attribute
Date: Thu, 12 Nov 2015 08:53:00 -0000 [thread overview]
Message-ID: <20151112085301.GW5675@tucnak.redhat.com> (raw)
In-Reply-To: <564378BB.8050400@acm.org>
On Wed, Nov 11, 2015 at 12:19:55PM -0500, Nathan Sidwell wrote:
> this patch implements default data attribute determination. The current
> behaviour defaults to 'copy' and ignores 'default(none)'. The patch
> corrects that.
>
> 1) We emit a diagnostic when 'default(none)' is in effect. The fortran FE
> emits some artificial decls that it doesn't otherwise annotate, which is why
> we check DECL_ARTIFICIAL. IIUC Cesar had a patch to address that but it
> needed some reworking?
I don't think treating DECL_ARTIFICIAL specially is a bug of any kind,
there are tons of different artificals even for C/C++ VLAs etc., and user
has no way to put them into any clauses explicitly, so what we do with them
is GCC internal thing.
> 2015-11-11 Nathan Sidwell <nathan@codesourcery.com>
>
> gcc/
> * gimplify.c (oacc_default_clause): New.
> (omp_notice_variable): Call it.
>
> gcc/testsuite/
> * c-c++-common/goacc/data-default-1.c: New.
>
> libgomp/
> * testsuite/libgomp.oacc-c-c++-common/default-1.c: New.
+ error ("%qE not specified in enclosing OpenACC %s construct",
+ DECL_NAME (lang_hooks.decls.omp_report_decl (decl)), rkind);
+ error_at (ctx->location, "enclosing OpenACC %s construct", rkind);
I'd use %qs instead of %s.
Otherwise ok.
Jakub
next prev parent reply other threads:[~2015-11-12 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 17:20 Nathan Sidwell
2015-11-12 8:53 ` Jakub Jelinek [this message]
2015-11-12 13:48 ` Nathan Sidwell
2015-11-12 20:22 David Edelsohn
2015-11-12 20:53 ` Nathan Sidwell
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=20151112085301.GW5675@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=cesar_philippidis@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.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).