From owner-freebsd-ppc@FreeBSD.ORG Mon Dec 8 15:13:49 2008 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F352F1065753 for ; Mon, 8 Dec 2008 15:13:48 +0000 (UTC) (envelope-from jrh29@alumni.cwru.edu) Received: from beta.eecs.cwru.edu (beta.EECS.CWRU.Edu [129.22.150.110]) by mx1.freebsd.org (Postfix) with ESMTP id A53468FC23 for ; Mon, 8 Dec 2008 15:13:48 +0000 (UTC) (envelope-from jrh29@alumni.cwru.edu) Received: from narn.knownspace ([::ffff:69.140.221.138]) (AUTH: PLAIN jrh29, TLS: TLSv1/SSLv3,168bits,DES-CBC3-SHA) by beta.eecs.cwru.edu with esmtp; Mon, 08 Dec 2008 10:13:31 -0500 id 00004AC7.493D399B.00004F20 Date: Mon, 8 Dec 2008 10:13:08 -0500 From: Justin Hibbits To: freebsd-ppc@freebsd.org Message-ID: <20081208151307.GA41398@narn.knownspace> References: <1228748788.1832.18.camel@horst-tla> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1228748788.1832.18.camel@horst-tla> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: Sane CFLAGS. X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 15:13:49 -0000 On Tue, Dec 09, 2008 at 02:06:28AM +1100, Horst Günther Burkhardt III wrote: > Hey y'all. > > FreeBSD is working a treat. > > Except for one little thing. > > I changed my CFLAGS in make.conf - then compiled a HEAP of stuff. Which > mostly now just spits out SIGILL. > > I have a PowerMac3,3 - Power Macintosh G4, 400MHz with 1MB cache. > > my CFLAGS were -Os -pipe -mcpu=7400 -mtune=7400 -maltivec -mabi=altivec > > I later changed that -Os to -O2 to no effect. > > What happened? Can I please have some advice regarding CFLAGS to set? > > (I'm contemplating removing altivec but would like advice from those > more experienced than I.) > > Thanks, > -- Horst. Your problem is Altivec - there is no altivec support in the kernel yet, so you'll get SIGILL whenever it hits an altivec instruction. - Justin