Hello, On Fri, Jul 3, 2020 at 10:06 AM Jakub Jelinek <ja...@redhat.com> wrote:
> On Thu, Jul 02, 2020 at 06:58:49PM -0400, y2s1982 . via Gcc wrote: > > This is giving me more clarity on what I have to do. At the moment, I am > > storing the > > information in the handle. > > > > I do have one problem: in 5.5.2.1 ( > > https://www.openmp.org/spec-html/5.0/openmpsu214.html#x270-18090005.5.2) > > it states that the call may verify the version compatibility using the > > context. > > How should I handle this? > > It is up to the implementation to decide what can it handle and what it > can't, the OMPD will be evolving, new callbacks will be added, old ones > deprecated etc. > As initially there will be just a single version supported (the 5.0 one), > until 5.1 is implemented we should just reject any incompatible versions, > and only when we implement 5.1 decide if we can accept 5.0 requests. > Thank you for the clarity on this. The task seems simple for now with respect to version compatibility. Still, following the documentation 5.5.2.1, how should I extract version information from ompd_address_space_context_t that is owned by the debugger instead of the OMPD to check for compatibility , especially when it is not currently defined? Should I leave that portion for later? Cheers, Tony Sim > > Jakub > >
