From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 22:02:24 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C5A16A4CE; Thu, 24 Mar 2005 22:02:24 +0000 (GMT) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02BBC43D55; Thu, 24 Mar 2005 22:02:24 +0000 (GMT) (envelope-from mkb@mkbuelow.net) Received: from drjekyll.mkbuelow.net (pD9E69236.dip.t-dialin.net [217.230.146.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 4A50632380; Thu, 24 Mar 2005 23:02:14 +0100 (CET) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j2OM3A0x002162; Thu, 24 Mar 2005 23:03:16 +0100 (CET) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j2OM2x0t002161; Thu, 24 Mar 2005 23:02:59 +0100 (CET) (envelope-from mkb) Date: Thu, 24 Mar 2005 23:02:59 +0100 From: Matthias Buelow To: Scott Long Message-ID: <20050324220259.GA770@drjekyll.mkbuelow.net> References: <200503232122.01937.peter@wemm.org> <86acosykew.fsf@xps.des.no> <42431F9D.5080906@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42431F9D.5080906@samsco.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: undefined reference to `memset' X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2005 22:02:24 -0000 Scott Long writes: >No it doesn't. See the gymnastics that Bill Paul had to do recently in >the iee80211 code to get around the insane inlining that gcc does with >-O2. I'm not saying that gcc produces incorrect code, but I am saying >that there is very strong evidence that it produces code that is >incompatible with the restrictions inherent to the kernel, mainly that >stack space is not infinite. I wonder how this is being done elsewhere, on NetBSD, everything is built with -O2 and has been for several years afair. Not that I care much about it but apparently it doesn't seem to be such a big problem everywhere? mkb.