Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!kddlab!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: <215@titccy.cc.titech.ac.jp>
Date: 20 May 91 19:53:14 GMT
References: <184@titccy.cc.titech.ac.jp> <1991May16.002617.15386@ladc.bull.com> <197@titccy.cc.titech.ac.jp> <7916@auspex.auspex.com>
Sender: news@titccy.cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 26

In article <7916@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:

>Are there any architectures of interest in this discussion that can't
>support PC-relative references?

R3000.

>If you believe that a system with a virtual-address cache, or a system
>with inverted page tables, cannot map several virtual addresses to a
>physical address, you're wrong.

I am correct. It can't map them.

>Proof by counterexample:

>They may have to go through some amount of pain to do so, but they *do*
>manage to do it.

As the architechture can not map them, a possible workaround is to flush
cache/page-table by software at context switch.

It will slow down context switch. That is, if you have heavily interactive
processes, as is often the case with window systems, the performance
degradation will be much.

						Masataka Ohta