On Mon, Jun 22, 2020 at 03:14:44PM -0400, y2s1982 . via Gcc wrote:
> > > If the 4 separate bytes of the version isn't something written somewhere
> > in
> > > the standard, I'd use something along the lines of
> > > #define GCC_VERSION (__GNUC__ * 1000 + __GNUC_MINOR__)
> > > macro, so make it
> > > #define OMPD_VERSION (5 * 10000 + 0 * 100 + 0)
> > > so there is some room for minor revisions below that.
> >
> > I may be mistaken, but I believe OpenMP version information is
> > provided in the OPENMP macro. It is a date,and it is used to detect
> > the conformance level of OpenMP.
We do define _OPENMP macro, but right now only to the 4.5 value because
OpenMP 5.0 is not fully supported yet.
If LLVM ompd_get_version returns that (5 << 24) + ..., then it seems to be
non-conforming, as there is:
"The OMPD API version number is equal to the value of the
_OPENMP macro defined in the associated OpenMP implementation, if the C
preprocessor is
supported."
So, please just return 201811, which is the value _OPENMP will eventually be
changed to.
Jakub
