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/95551] [OpenMP, OpenACC] -fopenmp/-fopenacc also with -foffload=disable fails with: (.gnu.offload_vars+0x0): undefined reference to `A.10.2' Date: Fri, 05 Jun 2020 10:09:51 +0000 [thread overview] Message-ID: <bug-95551-4-GZVh0YscD3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95551-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95551 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |94848 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- See also PR 94848 – the error is slightly different but similar enough that it might have the same cause. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94848 [Bug 94848] [Offloading][LTO] error due to only partially eliminated var / -ftree-pre causes link errors | libgomp.fortran/use_device_ptr-optional-3.f90 failures
next prev parent reply other threads:[~2020-06-05 10:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-05 10:06 [Bug middle-end/95551] New: " burnus at gcc dot gnu.org 2020-06-05 10:09 ` burnus at gcc dot gnu.org [this message] 2020-06-05 13:50 ` [Bug middle-end/95551] " burnus at gcc dot gnu.org 2020-06-05 14:33 ` jakub at gcc dot gnu.org 2020-06-08 10:50 ` burnus at gcc dot gnu.org 2020-06-08 21:25 ` cvs-commit at gcc dot gnu.org 2020-06-15 9:07 ` cvs-commit at gcc dot gnu.org 2020-06-15 9:11 ` burnus at gcc dot gnu.org 2020-06-15 9:11 ` 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-95551-4-GZVh0YscD3@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).