public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iverbin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63979] [openacc] undefined reference to main._omp_fn.x
Date: Thu, 20 Nov 2014 11:09:00 -0000	[thread overview]
Message-ID: <bug-63979-4-l7h3hO1LIy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63979-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63979

--- Comment #2 from Ilya Verbin <iverbin at gmail dot com> ---
I tried to reproduce this issue using trunk gcc and OpenMP:

gcc -fopenmp -flto -flto-partition=balanced -lgfortran -save-temps
libgomp/testsuite/libgomp.fortran/target2.f90

But all functions are privatized, e.g. __target2_MOD_foo._omp_fn.3.lto_priv.5,
it's exported as global hidden in partition 1, and referenced in the offload
table in partition 0 as it was planned.

We should figure out why in your case main._omp_fn.19 and main._omp_fn.20 were
not marked as global...


  parent reply	other threads:[~2014-11-20 11:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 20:03 [Bug other/63979] New: " vries at gcc dot gnu.org
2014-11-19 20:05 ` [Bug other/63979] " vries at gcc dot gnu.org
2014-11-20 11:09 ` iverbin at gmail dot com [this message]
2014-11-20 15:27 ` bernds at gcc dot gnu.org
2014-11-20 17:27 ` vries at gcc dot gnu.org
2014-11-20 17:34 ` iverbin at gmail dot com
2014-11-20 21:38 ` vries at gcc dot gnu.org
2014-11-20 21:39 ` vries at gcc dot gnu.org
2014-11-20 21:42 ` vries at gcc dot gnu.org
2014-11-20 23:39 ` iverbin at gmail dot com

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-63979-4-l7h3hO1LIy@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: 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).