From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <7c8f9ee75eee1c9d33beb57da78e298e@quintile.net> <20120712055118.2e15abf3@vardo.ethans.dre.am> Date: Tue, 17 Jul 2012 22:56:34 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cdf1342ad1f2f04c50d9efa Subject: Re: [9fans] 8c and elf shared libraries Topicbox-Message-UUID: a3372d4a-ead7-11e9-9d60-3106f5b1d025 --000e0cdf1342ad1f2f04c50d9efa Content-Type: text/plain; charset=UTF-8 I don't think any of them generate the right addressing to implement a dynamic library (in the Linux style). Data is addressed directly, assuming one data per text. Dynamic libraries need to create a data segment for each application sharing the library text, so the references to the data somehow need to be indirect. There is usually some form of indirect linkage to do that, although I don't know the details for the Linux/ELF variant. --000e0cdf1342ad1f2f04c50d9efa Content-Type: text/html; charset=UTF-8 I don't think any of them generate the right addressing to implement a dynamic library (in the Linux style).
Data is addressed directly, assuming one data per text. Dynamic libraries need to create a data segment
for each application sharing the library text, so the references to the data somehow need to be indirect.
There is usually some form of indirect linkage to do that, although I don't know the details for the Linux/ELF variant.

--000e0cdf1342ad1f2f04c50d9efa--