This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gomp4] Some progress on #pragma omp simd
- From: Aldy Hernandez <aldyh at redhat dot com>
- To: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Richard Henderson <rth at redhat dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 01 May 2013 11:01:54 -0500
- Subject: Re: [gomp4] Some progress on #pragma omp simd
- References: <20130419132957 dot GE12880 at tucnak dot redhat dot com> <5175B40F dot 7040709 at redhat dot com> <20130423135455 dot GN12880 at tucnak dot redhat dot com> <BF230D13CA30DD48930C31D40993300032A37760 at FMSMSX101 dot amr dot corp dot intel dot com> <20130424060117 dot GV12880 at tucnak dot redhat dot com> <51813A07 dot 4040105 at redhat dot com> <BF230D13CA30DD48930C31D409933000333DDA70 at ORSMSX153 dot amr dot corp dot intel dot com>
On 05/01/13 10:58, Iyer, Balaji V wrote:
Well, it looks like things are bit simpler than expected.
Multiple vectorlength clauses are being deprecated or eliminated
in the upcoming spec. So it looks like vectorlength is the same
thing as the safelen clause.
If you agree then I can get rid of OMP_CLAUSE_CILK_VECTORLENGTH
and just emit an OMP_CLAUSE_SAFELEN.
Agreed?
To my best knowledge, Yes. I believe safelen requires/allows only 1
value, so we should do what Jakub mentioned (vectorlength (a, b, c))
should be converted to safelen (max(a,b,c))
Well, we don't even need to do max(a,b,c) because according to the Cilk
Plus forum, the upcoming spec does not allow multiple vectorlength
clauses (or arguments), so only vectorlength(const_expr) is allowed.
Did I misunderstand something here?