From: Nathan Sidwell <nathan@acm.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: ilya.verbin@intel.com, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: offload data version number
Date: Thu, 06 Aug 2015 19:52:00 -0000 [thread overview]
Message-ID: <55C3BB0B.4040100@acm.org> (raw)
In-Reply-To: <55BD5F0F.6040801@acm.org>
Ping?
1) updated version patch https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00010.html
2) https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00204.html
An infrastructure piece from Thomas, who noticed liboffloadmic didn't have the
include paths to #include gomp-constants.h.
nathan
On 08/02/15 02:06, Nathan Sidwell wrote:
> On 07/31/15 12:10, Jakub Jelinek wrote:
>
>> This will hopefully be just GOMP_4.1 instead in the end, but it can
>> change when gomp-4_1-branch is merged to trunk, we don't guarantee
>> ABI stability at this point.
>
> Sure.
>
>> I'd prefer version to go after devicep argument rather than before.
> Fixed.
>
>> And really don't have ver_func vs. unver_func, just a single
>> callback that will take the version argument too (again, if possible
>> after target_id).
>
> Fixed (& elsewhere). The patch should be checked for intelmic if possible
> (Ilya?). The changes there are very mechanical so I'm not expecting a problem.
>
> We don't need to make the initial value of GOMP_VERSION non-zero, because the
> absence of the GOMP_OFFLOAD_version func will distinguish out of date plugins at
> this point.
>
>
>>> +
>>> + if (DLSYM_OPT (version, version))
>>
>> I'd prefer requiring version always (i.e. DLSYM (version);
>> plus the v != GOMP_VERSION checking).
>
> Fixed.
>
> ok? I'll commit a version of this to gomp4 branch shortly.
>
> nathan
>
next prev parent reply other threads:[~2015-08-06 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 13:28 Nathan Sidwell
2015-07-21 16:02 ` Nathan Sidwell
2015-07-24 14:21 ` Nathan Sidwell
2015-07-24 16:35 ` Jakub Jelinek
2015-07-24 16:46 ` Ilya Verbin
2015-07-24 17:22 ` Nathan Sidwell
2015-07-24 19:51 ` Nathan Sidwell
2015-07-24 20:02 ` Ilya Verbin
2015-07-24 20:05 ` Nathan Sidwell
2015-07-31 12:30 ` Nathan Sidwell
2015-07-31 14:08 ` Nathan Sidwell
2015-07-31 16:20 ` Jakub Jelinek
2015-08-02 0:06 ` Nathan Sidwell
2015-08-02 0:20 ` Nathan Sidwell
2015-08-03 11:16 ` Thomas Schwinge
2015-08-03 13:26 ` Nathan Sidwell
2015-08-04 16:19 ` Thomas Schwinge
2015-08-04 16:20 ` Nathan Sidwell
2015-08-06 19:52 ` Nathan Sidwell [this message]
2015-08-10 20:00 ` Thomas Schwinge
2015-08-24 8:45 ` Jakub Jelinek
2015-07-27 15:21 ` Nathan Sidwell
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=55C3BB0B.4040100@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ilya.verbin@intel.com \
--cc=jakub@redhat.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).