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/95622] force_output flag on a variable prevents optimization / regresses c-c++-common/goacc/kernels-alias-ipa-pta-2.c Date: Wed, 10 Jun 2020 09:18:56 +0000 [thread overview] Message-ID: <bug-95622-4-oOtr89pAmu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95622 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Dunno, perhaps there is a better way than force_output, how exactly we represent void *refs[] __attribute__((used)) = { &var1, &var2, &var3 }; where we say the array can't be optimized away and thus the referenced vars can't be optimized away? Does that also prevent such an optimization? For these vars, all we want to ensure is that the vars aren't optimized away, but don't need to derive from that that some other code could be accessing those vars indirectly. Or, shall we support putting NULL (or some other magic value) into the tables on the host or offload side if those vars have been optimized away completely on the host (or offload) sides? At least when not doing the not yet supported offloading from offload device back to host, perhaps a variable optimized away completely on the host will mean we can't every lookup such variable's address and so nothing needs to be recorded in the splay trees. But, if something is completely unused on the offload side but used on the host side, one can still try to e.g. map those variables and should get the address of the device var even if it is otherwise unused.
next prev parent reply other threads:[~2020-06-10 9:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-10 9:08 [Bug middle-end/95622] New: " burnus at gcc dot gnu.org 2020-06-10 9:18 ` jakub at gcc dot gnu.org [this message] 2020-06-12 10:58 ` [Bug middle-end/95622] [11 Regression] force_output flag on a variable prevents optimization / regresses c-c++-common/goacc/kernels-alias-ipa-pta{-2,-4,}.c tschwinge at gcc dot gnu.org 2020-06-12 13:10 ` burnus at gcc dot gnu.org 2020-06-16 13:15 ` cvs-commit at gcc dot gnu.org 2020-06-16 13:22 ` cvs-commit at gcc dot gnu.org 2020-07-15 6:56 ` rguenth at gcc dot gnu.org 2020-07-15 7:06 ` burnus at gcc dot gnu.org 2021-01-14 9:00 ` rguenth at gcc dot gnu.org 2021-03-25 18:28 ` burnus at gcc dot gnu.org 2021-03-26 8:21 ` rguenther at suse dot de 2021-04-27 11:39 ` [Bug middle-end/95622] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:02 ` [Bug middle-end/95622] [11/12/13/14 " jakub 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-95622-4-oOtr89pAmu@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).