public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/94320] [OpenMP][Offloading] lto1 ICE during IPA pass: inline – offline_size at gcc/ipa-inline-analysis.c:453 Date: Thu, 26 Mar 2020 09:50:04 +0000 [thread overview] Message-ID: <bug-94320-4-cTKR0Wnnvw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94320-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94320 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #1) > tried > + && !lto_stream_offload_p With that patch, I get 6 times "has been referenced in offloaded code but hasn't been marked to be included in the offloaded code". Thus, that's a useful patch for the code I looked at. All those those functions are template functions. (With -O0, the nvptx run-time compilers complains only about 3 of those functions.) > I'm afraid we need to actually implement properly the OpenMP 5.0 > automatic omp declare target discovery Yes, it looks like that. I think C++ code is mostly affected as one quickly ends up using 'operator[]' and similar functions, which are not always inlined. Additionally, template programming makes it harder for the user to mark those functions as 'declare target'.
prev parent reply other threads:[~2020-03-26 9:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-25 11:26 [Bug lto/94320] New: " burnus at gcc dot gnu.org 2020-03-25 11:39 ` [Bug lto/94320] " jakub at gcc dot gnu.org 2020-03-26 9:50 ` burnus at gcc dot gnu.org [this message]
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=bug-94320-4-cTKR0Wnnvw@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).