From: "Kevin D. Kissell" <kevink@mips.com>
To: "Jay Carlson" <nop@nop.com>, <linux-mips@oss.sgi.com>,
<linuxce-devel@linuxce.org>
Subject: Re: snow, a statically linked shared library MIPS ABI
Date: Thu, 22 Mar 2001 15:21:48 +0100 [thread overview]
Message-ID: <013a01c0b2db$749249a0$0deca8c0@Ulysses> (raw)
In-Reply-To: KEEOIBGCMINLAHMMNDJNAEHDCAAA.nop@nop.com
> Instead, we can build shared library images located at fixed locations
> in memory, with the location configured at library creation time.
> Stub libraries are generated that hold the absolute addresses of
> functions and data within the library image; programs (and other
> libraries) link with the stubs.
In fact, this is exactly how shared libraries worked under
UNIX System V. It is inelegant, but economical.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Jay Carlson <nop@nop.com>,
linux-mips@oss.sgi.com, linuxce-devel@linuxce.org
Subject: Re: snow, a statically linked shared library MIPS ABI
Date: Thu, 22 Mar 2001 15:21:48 +0100 [thread overview]
Message-ID: <013a01c0b2db$749249a0$0deca8c0@Ulysses> (raw)
Message-ID: <20010322142148.qJ3bj-h-gMLGxsujb3vxXtmuUYvsXnfKhE-MRLZeK5Y@z> (raw)
In-Reply-To: KEEOIBGCMINLAHMMNDJNAEHDCAAA.nop@nop.com
> Instead, we can build shared library images located at fixed locations
> in memory, with the location configured at library creation time.
> Stub libraries are generated that hold the absolute addresses of
> functions and data within the library image; programs (and other
> libraries) link with the stubs.
In fact, this is exactly how shared libraries worked under
UNIX System V. It is inelegant, but economical.
Kevin K.
next prev parent reply other threads:[~2001-03-22 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 13:23 snow, a statically linked shared library MIPS ABI Jay Carlson
2001-03-22 13:23 ` Jay Carlson
2001-03-22 14:21 ` Kevin D. Kissell [this message]
2001-03-22 14:21 ` Kevin D. Kissell
2001-03-22 15:28 ` Jay Carlson
2001-03-22 15:28 ` Jay Carlson
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='013a01c0b2db$749249a0$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=linuxce-devel@linuxce.org \
--cc=nop@nop.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