public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christophe dot guillon at st dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/23756] Missed optimization for PIC code with internal visibility
Date: Thu, 28 Jan 2010 16:20:00 -0000	[thread overview]
Message-ID: <20100128162028.21175.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23756-7904@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from christophe dot guillon at st dot com  2010-01-28 16:20 -------
Thanks for the detailled reply, I fully agree with your points:
- first, indeed, it's a matter of choice in the ABI (or compiler), the
assumption would be that a function that call another function of the same
module
(or a function of an undetermined module) must set the GP as soon as its own
visibility is hidden or more visible. What happens actually on the code that I
am optimizing is that generally it is better to have the parent function
setting the GOT pointer and that most of the time it is set anyway. Hence I
just observe that this choice, which is made on some architectures is a good
trade-off. 
 Thus it is indeed a request for enhancement on the pair ABI/compiler.
- second, it will be a good motivating case in the context of interprocedural
analysis.
 It can be considered in this case as a request for enhancement in the
interprocedural analysis framework.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23756


  parent reply	other threads:[~2010-01-28 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23756-7904@http.gcc.gnu.org/bugzilla/>
2010-01-28 14:54 ` christophe dot guillon at st dot com
2010-01-28 14:55 ` christophe dot guillon at st dot com
2010-01-28 15:37 ` jakub at gcc dot gnu dot org
2010-01-28 16:20 ` christophe dot guillon at st dot com [this message]
     [not found] <bug-23756-4@http.gcc.gnu.org/bugzilla/>
2012-01-11 14:30 ` rguenth at gcc dot gnu.org
2005-09-06 20:41 [Bug c/23756] New: " guillaume dot melquiond at ens-lyon dot fr
2005-09-06 22:43 ` [Bug middle-end/23756] " pinskia at gcc dot gnu dot 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=20100128162028.21175.qmail@sourceware.org \
    --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).