From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] splitting the compiler From: forsyth@caldo.demon.co.uk MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-dragflqzewvdufzsncnvxnncqm" Message-Id: <20020228172559.F132C19A2C@mail.cse.psu.edu> Date: Thu, 28 Feb 2002 17:21:30 +0000 Topicbox-Message-UUID: 5c3ecd42-eaca-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-dragflqzewvdufzsncnvxnncqm Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit oh yes, i'd forgotten about the Clipper. i did Ka Kc and Kl for the Fairchild/Intergraph Clipper chip in a week (1992/3 Plan 9), but i wasn't working very hard. the Plan 9 assembler is nearly always at most an afternoon's effort. the time for the compiler varies quite a bit. the Clipper architecture was straightforward. the compiler was easy. most of the time was spent on the linker. Kl got to compensate for all the processor pipeline/scoreboard bugs. dreadful. nice architecture but buggy implementation. --upas-dragflqzewvdufzsncnvxnncqm Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-admin@cse.psu.edu> Received: from punt-1.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk id 1014916427:10:02010:1; Thu, 28 Feb 2002 17:13:47 GMT Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net id aa1001535; 28 Feb 2002 17:13 GMT Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id EEF8019A06; Thu, 28 Feb 2002 12:12:31 -0500 (EST) Delivered-To: 9fans@cse.psu.edu Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id A8855199E4 for <9fans@cse.psu.edu>; Thu, 28 Feb 2002 12:11:52 -0500 (EST) Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1) id 16gToi-000585-00 for 9fans@cse.psu.edu; Thu, 28 Feb 2002 16:54:04 +0000 Received: from GATEWAY by bath.ac.uk with netnews for 9fans@cse.psu.edu (9fans@cse.psu.edu) To: 9fans@cse.psu.edu Message-ID: <87bse9h7ni.fsf@becket.becket.net> Organization: University of California, Irvine Content-Type: text/plain; charset=us-ascii References: <15484.64496.974395.322869@nanonic.hilbert.space>, <87pu2qy1sk.fsf@becket.becket.net>, Subject: Re: [9fans] splitting the compiler Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.8 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Help: List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 28 Feb 2002 16:53:08 GMT ozan s yigit writes: > "Thomas Bushnell, BSG" writes: > > > I'm pretty familiar with GCC internals, and it's pretty darn > > portable. But perhaps there's a whole level of portability I'm > > missing. > > original poster meant retargeting (i think). with (say) lcc, all one has > to worry about is a relatively straight-forward code generator. a student > targeted it for ns32000 in about a week. i would expect no more time for > 8c, but estimate three to six months for gcc. Hrm, I retargeted GCC (back in the days of version 1) for the old Clipper chip in about a month. Thomas --upas-dragflqzewvdufzsncnvxnncqm--