All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: David Huggins-Daines <dhd@linuxcare.com>,
	parisc-linux@thepuffingroup.com, parisc@lists.linuxcare.com
Subject: Re: Millicode calls, GP register, ld -r
Date: Fri, 11 Aug 2000 06:30:36 -0600	[thread overview]
Message-ID: <1523.965997036@upchuck> (raw)
In-Reply-To: Your message of Fri, 11 Aug 2000 17:32:33 +1000. <Pine.LNX.4.21.0008111648380.29780-100000@front.linuxcare.com.au>


  In message <Pine.LNX.4.21.0008111648380.29780-100000@front.linuxcare.com.au>y
ou write:
  > 
  > Hi David,
  > 
  > On thinking about this $$dyncall issue a bit more, what use are PLABELs in
  > PIC code anyway?  As far as I can see, PLABELs are used for two things:
  > 1) to provide an unique address for a function
  > 2) as a place to hang argument relocation information
  > 
  > We're not doing (2), and (1) is satisfied by the value in the PLTGOT.
  > 
  > So...  I can turn a PLABEL reference into a GOT reference, which will
  > magically fix the $$dyncall problem.
  > 
  > Comments?
The other way it's used is to handle intra-space calls/returns.  I don't know
if that's an issue for y'all or not.

jeff

jeff

  reply	other threads:[~2000-08-11 18:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0008111413410.29780-100000@front.linuxcare.com.au>
2000-08-11  7:32 ` Millicode calls, GP register, ld -r Alan Modra
2000-08-11 12:30   ` Jeffrey A Law [this message]
2000-08-11 14:56     ` Matthew Wilcox
2000-08-11 16:43       ` John David Anglin
2000-08-11 20:23   ` David Huggins-Daines
2000-08-11 22:35     ` David Huggins-Daines
2000-08-12  0:17       ` Alan Modra
2000-08-12  1:35         ` Alan Modra
2000-08-12 15:23           ` David Huggins-Daines
2000-08-12 16:07             ` John David Anglin
2000-08-12 16:29               ` David Huggins-Daines
2000-08-12 18:13             ` Jeffrey A Law

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=1523.965997036@upchuck \
    --to=law@cygnus.com \
    --cc=alan@linuxcare.com.au \
    --cc=dhd@linuxcare.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=parisc@lists.linuxcare.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.