Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.unix.internals
Subject: Re: Fundamental defect of the concept of shared libraries
Keywords: ISC i386 shared libraries
Message-ID: <225@titccy.cc.titech.ac.jp>
Date: 22 May 91 05:19:42 GMT
References: <197@titccy.cc.titech.ac.jp> <7916@auspex.auspex.com> <215@titccy.cc.titech.ac.jp> <1991May22.063425.26144@kithrup.COM>
Sender: news@titccy.cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 35

In article <1991May22.063425.26144@kithrup.COM>
	sef@kithrup.COM (Sean Eric Fagan) writes:

>>>Are there any architectures of interest in this discussion that can't
>>>support PC-relative references?
>>R3000.
>
>	_foo:
>		<entrycode>
>		jal	foo1$
>	foo1$:
>		addu	$at, $31, 0
>
>Guess what:  we can now do PC-relative references.  And this isn't even 
>the most efficient way to do it.

You poor boy, such an old trick is already known to me. I sometimes use
the trick if it is possible.

The problem here is that "jal" is not PC-relative.

You had better write PC-relative (not actually) reference as

<		la	$at,foo1$
<	foo1$:

It is as PC-relative as your trick, but is called immediate addressing.

Of course, both of above are unusable in PIC.

>Score one for our side.

Sigh.

						Masataka Ohta