Effect of pre-standard simd

Paulius_V_ · ‎01-12-2017

Hello. I've encountered an a compiler failure when trying to compile a file with -02 and above. This happens on both 2016 and 2017 versions on Linux. Seems to happen after an inclusion of a parallel openmp simd region. Is threre a way to make the compiler spit out some sort of a report or get any additional insight as to why?

Cannot publish the source code.

Paulius_V_ · ‎01-12-2017

Found what was causing it:

#IFDEF A
!$omp parallel do simd default(shared) schedule(static)
#IFDEF B
!$omp simd
#ENDIF
#ENDIF

DO I=AA,BB
...
ENDDO

taking out the simd out of 'do simd' fixed it. Is there any difference in inlining the simd clause as opposed to having it on the next directive?

TimP · ‎01-17-2017

Effect of pre-standard simd directive and openmp4 may not be always identical. Ideally compiler should warn about possible conflict.

Catasprophic compiler failure