Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!aries!mcdonald From: mcdonald@aries.scs.uiuc.edu (Doug McDonald) Newsgroups: comp.arch Subject: Re: m88200 cache flushes on DG Aviion Message-ID: <1990Dec15.143354.8493@ux1.cso.uiuc.edu> Date: 15 Dec 90 14:33:54 GMT References: <1990Dec14.031745.8840@ux1.cso.uiuc.edu> <44118@mips.mips.COM> Sender: news@ux1.cso.uiuc.edu (News) Organization: School of Chemical Sciences, Univ. of Illinois at Urbana-Champaign Lines: 18 In article <44118@mips.mips.COM> mash@mips.COM (John Mashey) writes: > >WHAT'S THE PROGRAMMATIC INTERFACE FOR CACHE-FLUSHING (and any other >cache-manipulation operations) on your favorite machine? >ARE THERE ANY STANDARDS FOR SCUH THINGS ACROSS VENDORS? (I can hope :-) > >If nobody is working on standardizing the programmatic interface, >we probably should be, as a service to the industry... >-- This is not a job for the OS (the standardization, that is). It is a job for the languages. In some, like Fortran 77, of course, you can't execute data. But in C you can. Almost. The "almost" is unequivocally the worst failure of the ANSI C spec: it should have included a routine (or macro) that makes a section of data into a code area and returns a code pointer to it. Doug McDonald