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: [gomp4, committed] Handle nested loops in kernels regions


On Mon, Jul 13, 2015 at 10:19:56AM +0200, Thomas Schwinge wrote:
> > We rely on pass_lim to move the *.omp_data_i loads out of the loop nest. 
> > For the test-case, pass_lim was managing to move the load out of the 
> > inner loop, but not the outer loop, because the load was classified as 
> > 'MOVE_PRESERVE_EXECUTION'. By marking the *.omp_data_i load 
> > non-trapping, it's now classified as 'MOVE_POSSIBLE', and moved out of 
> > the loop nest.
> 
> Should this go into trunk already?  (Jakub?)

I think so.

> Do we need to audit the
> code for constructs that need similar treatment?

That might be helpful.

	Jakub


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