From owner-freebsd-alpha Wed Feb 12 1:42:29 2003 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82EEE37B401 for ; Wed, 12 Feb 2003 01:42:28 -0800 (PST) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06D7743F75 for ; Wed, 12 Feb 2003 01:42:28 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0043.cvx40-bradley.dialup.earthlink.net ([216.244.42.43] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18itPN-0006Ed-00; Wed, 12 Feb 2003 01:42:25 -0800 Message-ID: <3E4A16AB.1346163E@mindspring.com> Date: Wed, 12 Feb 2003 01:40:59 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Marcel Moolenaar Cc: alpha@FreeBSD.org Subject: Re: Open Watcom compiler References: <20030211003353.GA12187@athlon.pn.xcllnt.net> <20030212084617.GA98667@dragon.nuxi.com> <20030212092532.GA20618@ns1.xcllnt.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a421b483a1c6c2039dd16a0f70009c8878548b785378294e88350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Marcel Moolenaar wrote: > Porting OW will not be a waste of my time. Fixing the gcc'isms will. > The former I do out of interest, the latter will only be something > I could possibly do because nobody else has an interest in doing > it (so far). If you were to make the compiler run native on FreeBSD x86 as a result of a "cd /usr/ports/tools/xxx; make all install", I would be willing to go through and fix *all* the "GCC'isms" in a "make world" (ports gets to be someone else's problem), assuming the Watcom compiler supports the more equivalent of "linker sets" for data (e.g. for SYSINIT). You will also need to support alignment and structure packing primitives, so device driver code does not have to be rewritten as pure assembly. Getting the changes committed to FreeBSD would be your problem, but from my point of view, fixing those kinds of problems is trivial, and I'm willing to do the "trained monkey" work of doing it, if there's a compiler there. I haven't done this with TenDRA, because TenDRA has an overzealous preprocessor, and doesn't support inline assembly or linker sets adequately. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message