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 ipa/97119] Top level option to disable creation of IPA symbols such as .localalias is desired
Date: Mon, 21 Sep 2020 14:28:54 +0000 [thread overview]
Message-ID: <bug-97119-4-Ngh9jtn4Bj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97119-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97119
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
There is no way to turn all of these, and I'm afraid can't be.
E.g. for the OpenMP/OpenACC outlined bodies of constructs, they need to be
named somehow.
Sure, one can disable many other ways how to clone functions (e.g. effectively
imply all functions have noclone attribute), but it will not handle everything.
next prev parent reply other threads:[~2020-09-21 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 23:22 [Bug ipa/97119] New: " ali_gccbugzilla at emvision dot com
2020-09-21 11:19 ` [Bug ipa/97119] " marxin at gcc dot gnu.org
2020-09-21 14:12 ` ro at gcc dot gnu.org
2020-09-21 14:12 ` ro at gcc dot gnu.org
2020-09-21 14:28 ` jakub at gcc dot gnu.org [this message]
2020-09-21 19:18 ` ali_gccbugzilla at emvision dot com
2020-09-25 9:20 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-02 10:33 ` hubicka at gcc dot gnu.org
2024-02-02 22:42 ` ali_gccbugzilla at emvision dot com
2024-02-02 22:48 ` pinskia at gcc dot gnu.org
2024-02-03 1:40 ` ali_gccbugzilla at emvision 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-97119-4-Ngh9jtn4Bj@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).