From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 8c and elf shared libraries
Date: Tue, 17 Jul 2012 23:17:34 +0100 [thread overview]
Message-ID: <CAOw7k5jtjXeDoSCo+4cw8Fb_=zYkMvBDyXzxQgsLDuFA-YDROQ@mail.gmail.com> (raw)
In-Reply-To: <1147b9e4528b3aa45e18363520c4dd8c@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
Normally with these schemes you need to save and restore the module (data)
pointer appropriately for calls in and out of the library.
Each library has its own data. For the library to be used by Linux
applications you'd need to mimic the conventions expected by the Linux
programs closely. The code also needs to be position-independent (in most
of the methods I've seen).
The machines aren't well-suited for the software we now run. We spend quite
a bit of time emulating protected procedures and dynamic linkage.
On 17 July 2012 22:59, erik quanstrom <quanstro@quanstro.net> wrote:
> i wonder if you could use the gs global register trick
> and a bit of runtime setup to implement this.
>
> (ducks)
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1103 bytes --]
next prev parent reply other threads:[~2012-07-17 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:15 Steve Simon
2012-07-12 4:51 ` Ethan Grammatikidis
2012-07-12 5:42 ` erik quanstrom
2012-07-17 16:58 ` Ethan Grammatikidis
2012-07-17 21:16 ` Christopher Nielsen
2012-07-17 21:30 ` Steve Simon
2012-07-17 21:56 ` Charles Forsyth
[not found] ` <CAOw7k5iVQcNr-SnHVpnCb=FACtaYx8WMFA1oypAfDY1F9-P1Cw@mail.gmail.c>
2012-07-17 21:59 ` erik quanstrom
2012-07-17 22:17 ` Charles Forsyth [this message]
2012-07-17 23:22 ` hiro
2012-07-18 7:02 ` steve
2012-07-20 11:45 ` Ethan Grammatikidis
2012-07-28 10:40 ` Uriel
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='CAOw7k5jtjXeDoSCo+4cw8Fb_=zYkMvBDyXzxQgsLDuFA-YDROQ@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).