This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gomp4, committed] Handle nested loops in kernels regions
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Thomas Schwinge <thomas at codesourcery dot com>
- Cc: Tom de Vries <Tom_deVries at mentor dot com>, "gcc-patches at gnu dot org" <gcc-patches at gnu dot org>
- Date: Mon, 13 Jul 2015 10:36:42 +0200
- Subject: Re: [gomp4, committed] Handle nested loops in kernels regions
- Authentication-results: sourceware.org; auth=none
- References: <55A2618A dot 7050503 at mentor dot com> <87io9o1nbn dot fsf at kepler dot schwinge dot homeip dot net>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
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