public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: OpenACC middle end changes
Date: Thu, 18 Dec 2014 12:36:00 -0000	[thread overview]
Message-ID: <20141218123145.GI1667@tucnak.redhat.com> (raw)
In-Reply-To: <87mw6lrvrf.fsf@schwinge.name>

On Thu, Dec 18, 2014 at 01:24:20PM +0100, Thomas Schwinge wrote:
> Hi Jakub!
> 
> On Thu, 18 Dec 2014 13:15:38 +0100, Jakub Jelinek <jakub@redhat.com> wrote:
> > On Thu, Dec 18, 2014 at 01:02:22PM +0100, Jakub Jelinek wrote:
> > > On Thu, Dec 18, 2014 at 12:38:53PM +0100, Jakub Jelinek wrote:
> > > > So, is what is on the gomp-4_0-branch now all that you'd like to merge to
> > > > trunk now?
> 
> Basically, yes.  Only "basically", because there are still a few
> unaddressed review issues in the front ends -- which I'll look into now.
> (Meaning really: now.)  :-)
> 
> 
> Doing the "merge" as one big commit on trunk will be the easiest
> approach, of course.  Is that OK, or is there any requirement to single
> out any of the changes, such as the
> libgomp/testsuite/libgomp-test-support.exp file just discussed, or the
> libgomp »Offloading and Multi Processing Runtime Library« renaming, or
> anything else?

Doing one big merge is ok with me.  If one needs to bisect something, they
can look at the gomp-4_0-branch.

> > > > Has it been tested on nvptx?
> 
> I have always been testing on gomp-4_0-branch with ACC_DEVICE_TYPE=host
> and ACC_DEVICE_TYPE=host_nonshm, plus with ACC_DEVICE_TYPE=nvidia in an
> internal branch.  This branch corresponds to gomp-4_0-branch, but also
> includes a few patches related to offloading that Bernd has posted for
> trunk approval, but has not yet gotten approved.

Do you have a list of them (URLs)?  Have they been pinged?
Are they show stoppers for the offloading, or just some tests fail because
of that?

> > > > I guess we should test it with
> > > > XeonPhi offloading too to make sure it doesn't break.
> 
> Right.  Do you happen to be set up for such testing?  I have not yet
> managed to properly change my build/test scripts for
> x86_64-intelmicemul-linux-gnu.

Anyone with x86_64-linux should be able to test that (i.e. the emulation),
for real offloading (that ix x86_64-intelmic-linux-gnu) you supposedly need
2 libraries, some kernel module, some distro installed on the offloading
device and most importantly the hw.

> --- gcc/config.gcc
> +++ gcc/config.gcc
> @@ -2906,6 +2906,7 @@ esac
>  case ${target} in
>  *-intelmic-* | *-intelmicemul-*)
>  	tmake_file="${tmake_file} i386/t-intelmic"
> +	tm_file="${tm_file} i386/intelmic-offload.h"
>  	;;
>  esac
>  
> diff --git gcc/config/i386/intelmic-offload.h gcc/config/i386/intelmic-offload.h
> new file mode 100644
> index 0000000..dc346c7
> --- /dev/null
> +++ gcc/config/i386/intelmic-offload.h
> @@ -0,0 +1,35 @@
> +/* Definitions for Intel MIC offloading.
> +
> +   Copyright (C) 2014 Free Software Foundation, Inc.
> +
> +   This file is part of GCC.
> +
> +   GCC is free software; you can redistribute it and/or modify
> +   it under the terms of the GNU General Public License as published by
> +   the Free Software Foundation; either version 3, or (at your option)
> +   any later version.
> +
> +   GCC is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   Under Section 7 of GPL version 3, you are granted additional
> +   permissions described in the GCC Runtime Library Exception, version
> +   3.1, as published by the Free Software Foundation.
> +
> +   You should have received a copy of the GNU General Public License and
> +   a copy of the GCC Runtime Library Exception along with this program;
> +   see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
> +   <http://www.gnu.org/licenses/>.  */
> +
> +#ifndef INTELMIC_OFFLOAD_H
> +#define INTELMIC_OFFLOAD_H
> +
> +/* Support for OpenACC acc_on_device.  */
> +
> +#include "gomp-constants.h"
> +
> +#define ACCEL_COMPILER_acc_device GOMP_DEVICE_INTEL_MIC
> +
> +#endif

LGTM.

	Jakub

  reply	other threads:[~2014-12-18 12:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 17:04 Thomas Schwinge
2014-11-13 18:31 ` Jakub Jelinek
2014-11-13 19:09   ` Cesar Philippidis
2014-11-13 19:16     ` Jakub Jelinek
2014-11-14  1:27       ` Cesar Philippidis
2014-12-18 11:07   ` Thomas Schwinge
2014-12-18 11:39     ` Jakub Jelinek
2014-12-18 13:17       ` Thomas Schwinge
2014-12-18 11:17   ` Thomas Schwinge
2014-12-18 11:39     ` Jakub Jelinek
2014-12-18 12:11       ` Jakub Jelinek
2014-12-18 12:24         ` Jakub Jelinek
2014-12-18 12:31           ` Thomas Schwinge
2014-12-18 12:36             ` Jakub Jelinek [this message]
2014-12-18 13:12               ` Jakub Jelinek
2014-12-18 13:24                 ` Thomas Schwinge
2015-02-13 16:23                   ` Thomas Schwinge
2014-12-18 14:29     ` Jakub Jelinek
2014-12-18 15:10       ` libgomp offloading testing (was: OpenACC middle end changes) Thomas Schwinge
2014-12-18 16:31   ` OpenACC middle end changes Thomas Schwinge
2015-07-09 15:52   ` Merge DEF_GOACC_BUILTIN into DEF_GOMP_BUILTIN? (was: OpenACC middle end changes) Thomas Schwinge
2015-07-09 15:58     ` Jakub Jelinek
2014-11-13 22:15 ` OpenACC middle end changes Joseph Myers
2014-11-14 10:35 ` Richard Biener
2014-11-14 10:37   ` Jakub Jelinek
2014-11-16  1:46 ` Gerald Pfeifer
2014-11-19  3:02 ` Bernd Schmidt
2014-11-19 19:32   ` Bernd Schmidt
2014-11-19 20:07   ` Bernd Schmidt
2014-11-19 22:20     ` Jakub Jelinek
2015-02-20  9:48     ` Jakub Jelinek
2015-02-20 11:49       ` nvptx offloading: Tag entrypoint functions with a special attribute (was: OpenACC middle end changes) Thomas Schwinge
2014-11-20  3:25   ` OpenACC middle end changes Bernd Schmidt
2014-11-20  8:07     ` Jakub Jelinek
2014-11-20 13:15       ` Bernd Schmidt

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=20141218123145.GI1667@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=thomas@codesourcery.com \
    /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).