From: Tobias Burnus <tobias@codesourcery.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: *PING**2 – Re: [Patch] OpenMP: Handle cpp_implicit_alias in declare-target discovery (PR96390)
Date: Tue, 25 Aug 2020 18:58:12 +0200 [thread overview]
Message-ID: <588fb796-3ad9-b7cd-1ba9-28880ecf78ae@codesourcery.com> (raw)
In-Reply-To: <639fa69b-74e3-7013-73c9-d9f6bf5c5711@codesourcery.com>
And another PING.
On 8/17/20 9:17 AM, Tobias Burnus wrote:
> On 8/3/20 5:37 PM, Tobias Burnus wrote:
>> It turned out that the omp_discover_declare_target_tgt_fn_r
>> discovered all nodes – but as it tagged the C++ alias nodes
>> and not the streamed-out nodes, no device function was created
>> and one got link errors if offloading devices were configured.
>> (Only with -O0 as otherwise inlining happened.)
>>
>> (Testcase is based on a sollve_vv testcase which in turn was
>> based on an LLVM bugreport.)
>>
>> OK?
>>
>> Tobias
>>
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
next prev parent reply other threads:[~2020-08-25 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 15:37 Tobias Burnus
2020-08-17 7:17 ` *PING* – " Tobias Burnus
2020-08-25 16:58 ` Tobias Burnus [this message]
2020-08-31 15:53 ` Jakub Jelinek
2020-09-14 13:25 ` Tobias Burnus
2020-09-16 10:36 ` Jakub Jelinek
2020-09-16 23:15 ` Tobias Burnus
2020-09-22 7:11 ` Tobias Burnus
2020-09-22 7:36 ` Jakub Jelinek
2020-09-22 14:11 ` Tobias Burnus
2020-09-22 14:24 ` Jakub Jelinek
2020-09-22 15:39 ` Tobias Burnus
2020-09-23 13:52 ` Tobias Burnus
2020-09-23 14:06 ` Jakub Jelinek
2020-09-23 15:45 ` Tobias Burnus
2020-09-25 11:23 ` Jakub Jelinek
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=588fb796-3ad9-b7cd-1ba9-28880ecf78ae@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--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).