https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98699
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|WAITING |RESOLVED
CC| |burnus at gcc dot gnu.org
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Hi Bill – thanks for the report. However, in upcoming GCC 11 this has improved:
(default) F 1
OMP_MAX_ACTIVE_LEVELS=1 F 1
OMP_MAX_ACTIVE_LEVELS=4 T 4
That's in line with your CCE and Intel examples.
The documentation mentions this also – kind of. (It states what GCC does and
the new functions but does not spell out the deprecation:
https://gcc.gnu.org/onlinedocs/libgomp/omp_005fget_005fnested.html and
https://gcc.gnu.org/onlinedocs/libgomp/OMP_005fNESTED.html )
Regarding the deprecation warning, the source files contain the following.
Note that in order not to promise too much, _OPENMP is set to 201511 (= OpenMP
4.5).
For C/C++, 'omp.h.in':
#if defined(__GNUC__) && _OPENMP >= 201811
# define __GOMP_DEPRECATED_5_0 __attribute__((__deprecated__))
#else
# define __GOMP_DEPRECATED_5_0
#endif
...
extern void omp_set_nested (int) __GOMP_NOTHROW __GOMP_DEPRECATED_5_0;
extern int omp_get_nested (void) __GOMP_NOTHROW __GOMP_DEPRECATED_5_0;
And for Fortran (only 'omp_lib' module):
#if _OPENMP >= 201811
!GCC$ ATTRIBUTES DEPRECATED :: omp_get_nested, omp_set_nested
#endif
Thus, currently no deprecation warnings – but once the version is bumped, there
will be compile-time warnings.
See also: https://gcc.gnu.org/g:6fae7eda968db658c280ad6f94fe6906a15af0c9
Thus, I think it can be closed as FIXED. Feel free to reopen (or fill a new
bug) is more issues come up.
