public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/109819] [OpenMP][OpenACC] -fno-lto effectively disables offloading
Date: Thu, 11 May 2023 21:52:54 +0000	[thread overview]
Message-ID: <bug-109819-4-67B9v3pMAn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109819-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, we have to ensure that with -fno-lto linking, even if some or all
compilation units were compiled with -flto we don't actually use the
(non-offloading) LTO sections for the linking.
All we want is if there are any offloading LTO sections to use them regardless
of whether -flto was used or not (and let mkoffload decide whether to actually
compile it and for which offloading targets).

  reply	other threads:[~2023-05-11 21:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 21:17 [Bug middle-end/109819] New: " burnus at gcc dot gnu.org
2023-05-11 21:52 ` jakub at gcc dot gnu.org [this message]
2023-05-11 21:59 ` [Bug middle-end/109819] " 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-109819-4-67B9v3pMAn@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).