public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: gcc@gcc.gnu.org
Subject: Re: PATCH: Optimize protected call for i386
Date: Thu, 15 May 2003 00:44:00 -0000	[thread overview]
Message-ID: <20030515004114.GG9567@redhat.com> (raw)
In-Reply-To: <20030514165007.A10337@lucon.org>

On Wed, May 14, 2003 at 04:50:07PM -0700, H. J. Lu wrote:
> > If you take the address of foo, in *any* DSO, you will not be
> > using either R_386_PC32 or R_386_PLT32.  You'll be using either
> > R_386_32 or R_386_GOT32.
> 
> But the currrent gcc uses R_386_GOTOFF for address of a protected
> data or function symbol on x86 when PIC is used. I will say it is
> a bug.

Agreed.

> R_386_GOT32 should be used here. I can provide a testcase if asked.

File a PR so it does not get lost.


r~

  reply	other threads:[~2003-05-15  0:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030513013909.GQ2166@bubble.sa.bigpond.net.au>
     [not found] ` <20030512184927.A14308@lucon.org>
     [not found]   ` <20030513015330.GR2166@bubble.sa.bigpond.net.au>
     [not found]     ` <20030512185613.A14533@lucon.org>
     [not found]       ` <20030513020400.GS2166@bubble.sa.bigpond.net.au>
     [not found]         ` <20030512192302.A14731@lucon.org>
     [not found]           ` <20030513135912.GA966@bubble.sa.bigpond.net.au>
     [not found]             ` <20030513142716.A20059@lucon.org>
     [not found]               ` <20030514085453.GA957@bubble.sa.bigpond.net.au>
     [not found]                 ` <20030514074940.A2376@lucon.org>
2003-05-14 23:03                   ` Alan Modra
2003-05-14 23:27                     ` Richard Henderson
2003-05-14 23:50                       ` H. J. Lu
2003-05-15  0:44                         ` Richard Henderson [this message]
2003-05-14 23:51                       ` Alan Modra
2003-05-15  0:42                         ` Richard Henderson
2003-05-15  0:51                           ` Alan Modra

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=20030515004114.GG9567@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.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).