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 middle-end/109128] New: [Offload][OpenMP][OpenACC] Static linking with unused offload function will lead to mismatch number of offload fn/symbols Date: Tue, 14 Mar 2023 12:15:33 +0000 [thread overview] Message-ID: <bug-109128-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109128 Bug ID: 109128 Summary: [Offload][OpenMP][OpenACC] Static linking with unused offload function will lead to mismatch number of offload fn/symbols Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: openacc, openmp, wrong-code Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- gfortran -fopenmp one.f90 ar rcv libone.a one.o ranlib libone.a gfortran -fopenmp two.f90 -L. -lone With GCN, it prints: libgomp: Cannot map target functions or variables (expected 0, have 2) The issue seems to be related to the linker removing the the symbol from __OFFLOAD_TABLE__ (i.e. from the .gnu.offload_funcs sections, which has first/last the__offload_func_table and __offload_funcs_end symbols, whose pointer is put into the __OFFLOAD_TABLE__). But the removed symbol is still visible to the offload compiler, i.e. it ends up in the GOMP_register_var call as generated by gcc/config/{gcn,nvptx}/mkoffload.cc It is not quite clear which permutations work or cause problems. It seems as if the common block (both files have then '.comm' sections) is important. Whether 'libone.a' also fails or only '-L. -lone' seems to be inconsistent (some minor details). Additionally, having a libgomp library call also in the main program is also required. ==> one.f90 <== module m implicit none integer :: my_var common /my_common/ my_var contains integer function unused_func(n) result(res) integer :: n !$omp target map(from:res) firstprivate(n) res = 5*n !$omp end target end end module m ==> two.f90 <== use m implicit none integer :: A !$omp target enter data map(A) end
next reply other threads:[~2023-03-14 12:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-14 12:15 burnus at gcc dot gnu.org [this message] 2023-03-14 12:36 ` [Bug middle-end/109128] " tschwinge at gcc dot gnu.org 2023-03-14 13:07 ` burnus at gcc dot gnu.org 2023-03-30 14:42 ` burnus at gcc dot gnu.org 2023-03-30 19:12 ` burnus at gcc dot gnu.org 2023-03-30 20:00 ` burnus at gcc dot gnu.org 2023-03-31 8:39 ` tschwinge at gcc dot gnu.org 2023-05-02 17:20 ` burnus at gcc dot gnu.org 2023-05-11 8:09 ` cvs-commit at gcc dot gnu.org 2023-05-11 14:56 ` burnus at gcc dot gnu.org
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-109128-4@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).