public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/61886] [4.8/4.9/5 Regression] LTO breaks fread with _FORTIFY_SOURCE=2 Date: Tue, 03 Mar 2015 19:12:00 -0000 [thread overview] Message-ID: <bug-61886-4-HFt7oKW83o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61886-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61886 --- Comment #35 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Zack, happy to hear from you again! Indeed the problem back was quite sloppy and we kind of mixed up symbols, assembler names and declarations in not well defined way. I think the safest way to go is to build on the alias machinery. For weakref we already have sense of "syntactic alias" (those that ends up translated to their target symbols) and I did some auditing recently (motivated by ICF bugs). Currently we have node->weakref saying if symbol is weakref and we do have good part of code aware of this. I guess we can have node->syntactic_alias (better name welcome, perhaps transparent?) that express the fact that alias should get translated to the final symbol during RTL output the same way as we do weakref on targets where they are not supported. Then it is a question where we want to translate the duplicated declarations into these aliases. I guess I can do it within the visibility itself or the FEs can be responsible for it. We can also get more fancy and try to solve the GNU extern inline issues - have a syntactic alias with also has boddy associated with it. I will try to start pushing things this direction.
next prev parent reply other threads:[~2015-03-03 19:12 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61886-4@http.gcc.gnu.org/bugzilla/> 2014-07-23 10:58 ` [Bug lto/61886] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-07-23 11:13 ` rguenth at gcc dot gnu.org 2014-07-23 13:08 ` rguenth at gcc dot gnu.org 2014-07-23 13:37 ` hubicka at gcc dot gnu.org 2014-08-27 10:00 ` [Bug lto/61886] [4.8/4.9/5 " rguenth at gcc dot gnu.org 2014-08-27 14:51 ` hubicka at ucw dot cz 2014-08-28 8:20 ` rguenther at suse dot de 2014-09-08 0:42 ` hubicka at ucw dot cz 2014-09-08 7:53 ` rguenther at suse dot de 2014-10-06 20:23 ` hubicka at ucw dot cz 2014-10-06 20:34 ` jakub at redhat dot com 2014-10-06 22:08 ` jakub at redhat dot com 2014-10-06 22:19 ` hubicka at ucw dot cz 2014-10-06 22:38 ` jakub at redhat dot com 2014-10-06 22:44 ` hubicka at ucw dot cz 2014-10-07 5:46 ` hubicka at ucw dot cz 2014-10-07 9:24 ` jakub at gcc dot gnu.org 2014-10-07 9:35 ` jakub at gcc dot gnu.org 2014-10-07 19:49 ` hubicka at ucw dot cz 2014-10-08 7:37 ` rguenther at suse dot de 2014-10-08 8:25 ` jakub at gcc dot gnu.org 2014-10-08 10:42 ` rguenther at suse dot de 2014-10-08 17:49 ` hubicka at ucw dot cz 2014-12-01 12:31 ` rguenth at gcc dot gnu.org 2014-12-19 13:37 ` jakub at gcc dot gnu.org 2015-01-19 13:16 ` rguenth at gcc dot gnu.org 2015-02-11 8:29 ` rguenth at gcc dot gnu.org 2015-02-11 8:33 ` rguenth at gcc dot gnu.org 2015-02-11 9:15 ` hubicka at ucw dot cz 2015-02-11 10:05 ` rguenther at suse dot de 2015-02-11 16:30 ` zackw at panix dot com 2015-03-03 19:12 ` hubicka at gcc dot gnu.org [this message] 2015-03-20 21:00 ` hubicka at gcc dot gnu.org 2015-06-23 8:21 ` [Bug lto/61886] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:10 ` [Bug lto/61886] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:35 ` 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-61886-4-HFt7oKW83o@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).