This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"

From: Bernd Schmidt <bschmidt at redhat dot com>
To: Thomas Schwinge <thomas at codesourcery dot com>, Jakub Jelinek <jakub at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org, Tom de Vries <vries at codesourcery dot com>
Date: Thu, 11 Feb 2016 16:58:47 +0100
Subject: Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
Authentication-results: sourceware.org; auth=none
References: <87r3hac1w9 dot fsf at hertz dot schwinge dot homeip dot net> <569D2059 dot 4010105 at mentor dot com> <87d1subnu5 dot fsf at hertz dot schwinge dot homeip dot net> <87a8nyawph dot fsf at hertz dot schwinge dot homeip dot net> <20160122083625 dot GL3017 at tucnak dot redhat dot com> <56A22C2E dot 6000408 at redhat dot com> <20160122132538 dot GT3017 at tucnak dot redhat dot com> <56A22F37 dot 5010505 at redhat dot com> <87zivg8rcy dot fsf at hertz dot schwinge dot homeip dot net> <87h9hg9450 dot fsf at hertz dot schwinge dot homeip dot net> <56BB3A5E dot 6000506 at redhat dot com> <87d1s48w97 dot fsf at hertz dot schwinge dot homeip dot net> <56BB56EC dot 90707 at redhat dot com> <8737t08rgi dot fsf at hertz dot schwinge dot homeip dot net> <56BB674A dot 7050401 at redhat dot com> <87y4as79fw dot fsf at hertz dot schwinge dot homeip dot net> <56BB9881 dot 1070205 at redhat dot com> <87twlf7ego dot fsf at hertz dot schwinge dot homeip dot net>

On 02/11/2016 11:01 AM, Thomas Schwinge wrote:


The "avoid offloading" mechanism.  Owed to the non-shared-memory
offloading architecture, if the compiler/runtime decides to "avoid
offloading", then this has to apply to *all* code offloading, for data
consistency reasons.  Do we agree on that?

Not necessarily, I think. It should be possible to determine whethersome offloaded code blocks are independent from each other. (Thatdoesn't mean we currently have any good way of making such decisions.libgomp or even the ptx compiler are probably too late and don't havethe necessary information anymore).



Bernd

References:
- Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Thomas Schwinge
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Thomas Schwinge
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Bernd Schmidt
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Thomas Schwinge
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Bernd Schmidt
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Thomas Schwinge
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Bernd Schmidt
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Thomas Schwinge
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Bernd Schmidt
- Re: Un-parallelized OpenACC kernels constructs with nvptx offloading: "avoid offloading"
  - From: Thomas Schwinge

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]