From: Tobias Burnus <tobias@codesourcery.com>
To: Martin Jambor <mjambor@suse.cz>,
Mohamed Atef <mohamedatef1698@gmail.com>
Cc: <jakub@redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: GNU OMPD implementation
Date: Thu, 2 Dec 2021 09:37:16 +0100 [thread overview]
Message-ID: <0795356f-c6bb-7b85-3d1f-71987be699c0@codesourcery.com> (raw)
In-Reply-To: <ri6bl20fa20.fsf@suse.cz>
Hi,
On 01.12.21 19:35, Martin Jambor wrote:
> On Tue, Nov 30 2021, Mohamed Atef wrote:
>> Where is the variable of the OpenMP version defined?
The GCC code itself does not make a difference, contrary to
C/C++/Fortran which have -std=....
OpenMP 4.5 (also known as 201511) is fully supported (minus bugs). Thus,
that's the version number (201511) reported to the user. For Fortran,
the 'openmp_version' parameter in the module 'omp_lib' and in omp_lib.h
come from libgomp/omp_lib.f90.in and libgomp/omp_lib.h.in. For C/C++ (or
Fortran with -cpp for the preprocessor), the value is in _OPENMP and is
defined in gcc/c-family/c-cppbuiltin.c.
However, while GCC only claims 4.5/201511 support, OpenMP 5.0 and 5.1
are partially implemented, cf.
https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.html
Thus, when a later version of the spec changed behavior, GCC might not
have 4.5 semantic but 5.0, 5.1 or even 5.2 (or later) semantic. This
happens either when implementing a 5.x feature or when a bug in the spec
was found which has then be fixed.
For completeness, for exported symbols in libgomp, some versioning
exists, cf. libgomp/libgomp.map.
Thanks for working on OMPD!
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2021-12-02 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 4:57 Mohamed Atef
2021-11-29 13:55 ` Martin Jambor
2021-11-30 0:23 ` Mohamed Atef
2021-11-30 6:42 ` Mohamed Atef
2021-12-01 18:35 ` Martin Jambor
2021-12-02 8:37 ` Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-29 21:03 Mohamed Atef
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0795356f-c6bb-7b85-3d1f-71987be699c0@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mjambor@suse.cz \
--cc=mohamedatef1698@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).