From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] partial-Plan9ification question From: David Gordon Hogan MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-xfrfzcfawtgicfgpshiwkxvkyn" Message-Id: <20010712220824.80D9A199C0@mail.cse.psu.edu> Date: Thu, 12 Jul 2001 18:08:21 -0400 Topicbox-Message-UUID: c8dc808a-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-xfrfzcfawtgicfgpshiwkxvkyn Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit To quote the old Basser fortunes file: Don't patch bad code. Rewrite it. --upas-xfrfzcfawtgicfgpshiwkxvkyn Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu Jul 12 18:02:29 EDT 2001 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Thu Jul 12 18:02:22 EDT 2001 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 74F3C19A09; Thu, 12 Jul 2001 18:02:09 -0400 (EDT) Received: from smarty.smart.net (smarty.smart.net [207.176.80.102]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id A04B9199C0 for <9fans@cse.psu.edu>; Thu, 12 Jul 2001 18:01:48 -0400 (EDT) Received: (from humbubba@localhost) by smarty.smart.net (8.9.1/8.9.1) id SAA29875 for 9fans@cse.psu.edu; Thu, 12 Jul 2001 18:16:00 -0400 From: Rick Hohensee Message-Id: <200107122216.SAA29875@smarty.smart.net> To: 9fans@cse.psu.edu X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [9fans] partial-Plan9ification question Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.5 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 12 Jul 2001 18:16:00 -0400 (EDT) Hi. Given a POSIXy unix, with lots of inline assembly interlaced in the C with Gcc asm(""), consider losing all the asm("") in lieu of C-called assembly and inlined C. This presents a factoring problem for header files and so on relative to unix. Given also that Plan 9's header structure is the best for languages like C, and given that we want that Plan9ism, but not the cross-compile facilities any time soon, how would you restructure the sources? (I'll be presuming my whole world is one cpu.) I know I'll need a cpu.S, a cpu.o, but then things get variable. I'll also probably be doing ld-related #pragmas, and maybe a mk or a proto-mk in sh, but I don't know that that pertains to the above issue if I just assume one CPU. Care to comment, maestros? Rick Hohensee www.clienux.com --upas-xfrfzcfawtgicfgpshiwkxvkyn--