From owner-freebsd-hackers Mon Oct 19 13:43:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17005 for freebsd-hackers-outgoing; Mon, 19 Oct 1998 13:43:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16981 for ; Mon, 19 Oct 1998 13:43:11 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id QAA17966; Mon, 19 Oct 1998 16:44:46 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 19 Oct 1998 16:44:46 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: "Kaleb S. KEITHLEY" cc: hackers@FreeBSD.ORG Subject: Re: Producing non-GPLed tools for FreeBSD In-Reply-To: <362B9D4D.500216A0@ics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Oct 1998, Kaleb S. KEITHLEY wrote: > > the ABI for FreeBSD differs from that of System V in terms > > of parameter passing and register usage.... > > Where is the FreeBSD ABI documented? :-) > > Given that e.g. gcc generates code on SVR4 that works on SVR4 -- are you > saying that you think that gcc is, or should be generating different > code on FreeBSD because of ABI issues? It's not exactly convenient for > me to try it and see, but I'd be surprised if it is. > > I didn't steal the Intel supplement to the ABI when I left my last job, > but I don't recall that it specified parameter passing and register > usage, and the generic ABI doesn't speak to it (or if it does, it's not > in the index.) > if you go to the pgcc homepage (pentium optimized gcc) they have a lot of pointers to docs for this as i recall. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message