Linux PARISC architecture development
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@linuxcare.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: Lazy linking issues
Date: 26 Sep 2000 10:26:37 -0400	[thread overview]
Message-ID: <87em27kz4y.fsf@linuxcare.com> (raw)
In-Reply-To: Alan Modra's message of "Wed, 27 Sep 2000 01:21:24 +1100 (EST)"

Alan Modra <alan@linuxcare.com.au> writes:

> On Tue, 26 Sep 2000, Alan Modra wrote:
> 
> > Code at the start of the .plt looks like:
> > 	b,l	1f,%r26
> > 	depi	0,31,2,%r26
> > 1:	addil	LD'_GLOBAL_OFFSET_TABLE_ + 8 - ($PIC_pcrel$0 - 8),%r26
> > 	ldwm	RD'_GLOBAL_OFFSET_TABLE_ + 8 - ($PIC_pcrel$0 - 12)(%r1),%r26
> > 	copy	%r19,%r25
> > 	ldw	4(%r1),%r19
> > 	bv	%r0(%r26)
> > 	ldw	-4(%r1),%r26
> 
> That's all a bit silly.  How come no-one noticed and told me how foolish 
> I am?  We can't trash the arg registers willy-nilly.

Probably because I was asleep :)

> I'm going for a stub at the end of the .plt, with .plt and .got guaranteed
> to be glued together.  The fixup fptr will be immediately after the stub
> at the end of the .plt, ie. at got[-2] istead of got[2].

Okay.  I suppose I will take the same approach as the Alpha code does,
and look for a particular instruction at the end of the GOT in
elf_machine_runtime_setup() as an indication of whether lazy linking
can be done or not.

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

  reply	other threads:[~2000-09-26 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-26  0:39 [parisc-linux] Lazy linking issues David Huggins-Daines
2000-09-26  4:32 ` Alan Modra
2000-09-26  8:08   ` Alan Modra
2000-09-26 14:21     ` Alan Modra
2000-09-26 14:26       ` David Huggins-Daines [this message]
2000-09-26 14:45         ` 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=87em27kz4y.fsf@linuxcare.com \
    --to=dhd@linuxcare.com \
    --cc=alan@linuxcare.com.au \
    --cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox