[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Compilation of methods per class.
- To: gregor@parc.xerox.com
- Subject: Compilation of methods per class.
- From: Jon L White <jonl@lucid.com>
- Date: Tue, 25 Sep 90 17:04:03 PDT
- Cc: lange@CS.UCLA.EDU, rivieres@parc.xerox.com, faieta@parc.xerox.com, gerson@parc.xerox.com, brotsky@parc.xerox.com, bobrow@parc.xerox.com, kimber@parc.xerox.com, cutting@parc.xerox.com, robertso@parc.xerox.com, rodrigue@parc.xerox.com, rao@parc.xerox.com, haarslev@parc.xerox.com, cloops-arisia@arisia.Xerox.COM
- In-reply-to: Gregor Kiczales's message of Tue, 25 Sep 1990 16:28:25 PDT <90Sep25.162834pdt.269@spade.parc.xerox.com>
re: Date: Tue, 25 Sep 1990 10:55:09 PDT
From: Jon L White <jonl@lucid.com>
The circumstances you relate above are precisely the symptoms one would
expect when there is a breakdown in the assumptions underlying the PCL
generic-function caching technique.
Can you elaborate on this?
The assumption that breaks down is that most or all of the lookup
requests find the entry in the cache (first probe or "mirror" probe).
Unless the more recent PCL has changed algorithms, there are lots of
reasonable circumstances where there will be a "cache miss" path taken
even though the entry is present someplace in the cache.
-- JonL --