public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ali_gccbugzilla at emvision dot com" <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 19:18:47 +0000 [thread overview] Message-ID: <bug-97119-4-LrqlxFYGOp@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 --- Comment #5 from Ali Bahrami <ali_gccbugzilla at emvision dot com> --- I added -flive-patching=inline-only-static as suggested by Martin. It didn't alter the results I'm seeing. There is still a lot of .localalias in the resulting objects. Still, the optimizations it is documented as preventing all seem like the sort of things we wouldn't want for the core OS objects, so we probably should add this. I'm at a disadvantage here, as I don't fully understand how clone functions and .localalias symbols are related. From the gcc manpage, I gather that clones are copies made to do certain optimizations, such as elimination of constant arguments. In contrast, foo, and foo.localalias seen to be references to a single function, with the main different being that foo is global and foo.localias is local. I'm not sure what the benefit of the local symbol is, but since it references the same address, as the global, it's not what I would call a clone. In any event, I would be content with a way to disable these for straightforward C objects, as opposed to specialized cases like OpenMP/OpenACC, so perhaps there's a way to do that, even if the fully general case isn't possible? Thanks. - Ali
next prev parent reply other threads:[~2020-09-21 19:18 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 2020-09-21 19:18 ` ali_gccbugzilla at emvision dot com [this message] 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-LrqlxFYGOp@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).