public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: hjl@lucon.org (H. J. Lu)
Cc: aph@redhat.com (Andrew Haley),
	paolo.bonzini@lu.unisi.ch (Paolo Bonzini),
	        gcc-patches@gcc.gnu.org
Subject: Re: PATCH: Build shared libraries with -Bsymbolic-functions
Date: Sun, 14 Jan 2007 18:29:00 -0000	[thread overview]
Message-ID: <200701141830.l0EIU78u005241@localhost.localdomain> (raw)
In-Reply-To: <20070114154640.GA24001@lucon.org>

> I checked in the libjava part. Here is the updated patch for other
> libraries. If someone can give me a list of functions in libobjc
> which should be overridable, I will add them to the dynamic list
> for libobjc.

All except for the class functions themselves.  For libobjc, a better
way of doing this is actually marking the class methods as hidden as they
are never called directly.

-- Pinski

  reply	other threads:[~2007-01-14 18:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17827.39608.578446.917969@zebedee.pink>
     [not found] ` <20070109134100.GA17596@lucon.org>
     [not found]   ` <17827.40388.768818.387227@zebedee.pink>
     [not found]     ` <20070109135627.GA24284@lucon.org>
     [not found]       ` <17827.41041.498443.221842@zebedee.pink>
     [not found]         ` <20070109141819.GA4072@lucon.org>
     [not found]           ` <20070109174240.GA31750@lucon.org>
     [not found]             ` <20070109192047.GA32254@lucon.org>
     [not found]               ` <20070110142929.GA22520@lucon.org>
     [not found]                 ` <m3tzyzqaha.fsf@localhost.localdomain>
2007-01-10 19:03                   ` H. J. Lu
2007-01-10 22:49                     ` H. J. Lu
2007-01-11  8:04                     ` Paolo Bonzini
2007-01-11 18:15                       ` H. J. Lu
2007-01-11 18:33                         ` Paolo Bonzini
2007-01-11 20:09                           ` H. J. Lu
2007-01-12  7:57                             ` Paolo Bonzini
2007-01-12 14:39                               ` H. J. Lu
2007-01-12 18:52                                 ` H. J. Lu
2007-01-13 13:48                                   ` Paolo Bonzini
2007-01-13 14:51                                     ` H. J. Lu
2007-01-13 17:12                                     ` Andrew Pinski
2007-01-13 17:32                                       ` H. J. Lu
2007-01-14 13:04                                     ` Andrew Haley
2007-01-14 15:46                                       ` H. J. Lu
2007-01-14 18:29                                         ` Andrew Pinski [this message]
2007-01-14 18:47                                           ` H. J. Lu
2007-01-31 22:20                                             ` H. J. Lu
2007-01-31 22:24                                               ` Andrew Pinski
2007-01-31 22:42                                                 ` H. J. Lu
2007-02-10 23:28                                                   ` H. J. Lu
2007-02-11  9:09                                                     ` Andrew Pinski
2007-01-12 12:13                             ` Andrew Haley
2007-01-12 14:40                               ` H. J. Lu

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=200701141830.l0EIU78u005241@localhost.localdomain \
    --to=pinskia@physics.uc.edu \
    --cc=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl@lucon.org \
    --cc=paolo.bonzini@lu.unisi.ch \
    /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).