Re: [OpenACC 8/11] device-specific lowering

2015-10-27 Thread Nathan Sidwell
On 10/26/15 08:13, Jakub Jelinek wrote: On Wed, Oct 21, 2015 at 03:49:08PM -0400, Nathan Sidwell wrote: This patch is the device-specific half of the previous patch. It processes the partition head & tail markers and loop abstraction functions inserted during omp lowering. This is the patch

Re: [OpenACC 8/11] device-specific lowering

2015-10-26 Thread Nathan Sidwell
On 10/26/15 09:51, Jakub Jelinek wrote: If not, I think the only thing remaining is the IFN_UNIQUE patch, which (At least) needs an update to use targetm.have... conversion. Ok, will wait till you make those changes then? Hope to have that later today. nathan

Re: [OpenACC 8/11] device-specific lowering

2015-10-26 Thread Jakub Jelinek
On Mon, Oct 26, 2015 at 09:13:28AM -0700, Nathan Sidwell wrote: > On 10/26/15 08:13, Jakub Jelinek wrote: > > >>It won't convert them into such representations. > > > >Can you fix that incrementally? I'd expect that code marked with acc loop > >vector > >can't have loop carried backward lexical

Re: [OpenACC 8/11] device-specific lowering

2015-10-26 Thread Nathan Sidwell
On 10/26/15 08:13, Jakub Jelinek wrote: It won't convert them into such representations. Can you fix that incrementally? I'd expect that code marked with acc loop vector can't have loop carried backward lexical dependencies, at least not within the adjacent number of iterations specified in

Re: [OpenACC 8/11] device-specific lowering

2015-10-26 Thread Jakub Jelinek
On Wed, Oct 21, 2015 at 03:49:08PM -0400, Nathan Sidwell wrote: > This patch is the device-specific half of the previous patch. It processes > the partition head & tail markers and loop abstraction functions inserted > during omp lowering. > > I don't see anything that would e.g. set the various

Re: [OpenACC 8/11] device-specific lowering

2015-10-22 Thread Nathan Sidwell
On 10/22/15 05:31, Jakub Jelinek wrote: On Wed, Oct 21, 2015 at 03:49:08PM -0400, Nathan Sidwell wrote: So, how do you expand the OACC loops on non-PTX devices (host, or say XeonPhi)? Do you drop the IFNs and replace stuff with normal loops? On a non ptx target (canonical example being the

Re: [OpenACC 8/11] device-specific lowering

2015-10-22 Thread Jakub Jelinek
On Wed, Oct 21, 2015 at 03:49:08PM -0400, Nathan Sidwell wrote: > This patch is the device-specific half of the previous patch. It processes > the partition head & tail markers and loop abstraction functions inserted > during omp lowering. > > In the oacc_device_lower pass we scan the CFG reconst

Re: [OpenACC 8/11] device-specific lowering

2015-10-21 Thread Nathan Sidwell
This patch is the device-specific half of the previous patch. It processes the partition head & tail markers and loop abstraction functions inserted during omp lowering. In the oacc_device_lower pass we scan the CFG reconstructing the set of nested loops demarked by IFN_UNIQUE (HEAD_MARK) & I