Re: [patch] Fortran fix for PR70289

2016-04-04 Thread Cesar Philippidis
On 04/01/2016 08:17 AM, Jakub Jelinek wrote: > On Fri, Apr 01, 2016 at 08:07:24AM -0700, Cesar Philippidis wrote: >> On 04/01/2016 07:56 AM, Jakub Jelinek wrote: >>> On Fri, Apr 01, 2016 at 07:49:16AM -0700, Cesar Philippidis wrote: The bug in PR70289 is an assertion failure triggered by a sta

Re: [patch] Fortran fix for PR70289

2016-04-01 Thread Jakub Jelinek
On Fri, Apr 01, 2016 at 08:07:24AM -0700, Cesar Philippidis wrote: > On 04/01/2016 07:56 AM, Jakub Jelinek wrote: > > On Fri, Apr 01, 2016 at 07:49:16AM -0700, Cesar Philippidis wrote: > >> The bug in PR70289 is an assertion failure triggered by a static > >> variable used inside an offloaded acc r

Re: [patch] Fortran fix for PR70289

2016-04-01 Thread Cesar Philippidis
On 04/01/2016 07:56 AM, Jakub Jelinek wrote: > On Fri, Apr 01, 2016 at 07:49:16AM -0700, Cesar Philippidis wrote: >> The bug in PR70289 is an assertion failure triggered by a static >> variable used inside an offloaded acc region which doesn't have a data >> clause associated with it. Basically, th

Re: [patch] Fortran fix for PR70289

2016-04-01 Thread Jakub Jelinek
On Fri, Apr 01, 2016 at 07:49:16AM -0700, Cesar Philippidis wrote: > The bug in PR70289 is an assertion failure triggered by a static > variable used inside an offloaded acc region which doesn't have a data > clause associated with it. Basically, that static variable ends up in a > different lto pa

[patch] Fortran fix for PR70289

2016-04-01 Thread Cesar Philippidis
The bug in PR70289 is an assertion failure triggered by a static variable used inside an offloaded acc region which doesn't have a data clause associated with it. Basically, that static variable ends up in a different lto partition, which was not streamed to the offloaded compiler. I'm not sure if