Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!hsdndev!husc6!encore!pierson From: pierson@encore.com (Dan L. Pierson) Newsgroups: comp.sys.m88k Subject: Re: m88200 cache flushes on DG Aviion Message-ID: Date: 12 Dec 90 19:55:23 GMT References: <2308@io.UUCP> <1199@dg.dg.com> <4322@photon.oakhill.UUCP> Sender: news@Encore.COM Organization: Encore Computer Corporation Lines: 29 In-reply-to: meissner@osf.org's message of 12 Dec 90 03:13:08 GMT In article meissner@osf.org (Michael Meissner) writes: In article pierson@encore.com (Dan L. Pierson) writes: | 2. Manage dynamic space with a copying garbage collector. This | means that code may move between calls however the old code | location will only be reused after the entire semi-space it's | part of has been freed for reuse (there are less friendly GC | algorithms...). Beware that compilers for non-GC languages (like C), may cache a function's address in a register between calls. Obviously; that's a standard constraint when interfacing such languages to C and friends. It's also one of the reasons why technically inferior GC algorithms such as mark and sweep may actually work better for multi-language applications. This is rapidly becoming a digression from comp.sys.m88k. dan -- dan In real life: Dan Pierson, Encore Computer Corporation, Research UUCP: {talcott,linus,necis,decvax}!encore!pierson Internet: pierson@encore.com