From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 24 23:22:11 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 431B416A4CE for ; Thu, 24 Mar 2005 23:22:11 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9254843D5C for ; Thu, 24 Mar 2005 23:22:10 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j2ONM2X4010291; Thu, 24 Mar 2005 18:22:03 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Thu, 24 Mar 2005 18:22:00 -0500 User-Agent: KMail/1.6.2 References: <20050324214956.GA99087@dragon.NUXI.org> <1111702231.2655.6.camel@server.mcneil.com> In-Reply-To: <1111702231.2655.6.camel@server.mcneil.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Message-Id: <200503241822.00480.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/782/Thu Mar 24 07:29:35 2005 on anuket.mj.niksun.com X-Virus-Status: Clean 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 23:22:11 -0000 On Thursday 24 March 2005 05:10 pm, Sean McNeil wrote: > On Thu, 2005-03-24 at 13:49 -0800, David O'Brien wrote: > > Please don't top-post -- it destroys context. [Format recovered] > > > > On Thu, Mar 24, 2005 at 12:46:41PM -0800, Vinod Kashyap wrote: > > > > On Thu, Mar 24, 2005 at 06:05:17PM +1100, Peter Jeremy wrote: > > > > > On Wed, 2005-Mar-23 13:48:04 -0800, Vinod Kashyap wrote: > > > > > >If any kernel module has the following, or a similar line > > > > > > in it: ----- > > > > > >char x[100] = {0}; > > > > > >----- > > > > > >building of the GENERIC kernel on FreeBSD 5 -STABLE for > > > > > > amd64 as of 03/19/05, fails with the following message at > > > > > > the > > > > > > > > time of linking: > > > > > >"undefined reference to `memset'". > > > > > > > > > > > >The same problem is not seen on i386. > > > > > > > > > > > >The problem goes away if the above line is changed to: > > > > > >----- > > > > > >char x[100]; > > > > > >memset(x, 0, 100); > > > > > >----- > > > > > > > > > > Can you post a complete (compilable) example please. > > > > > > > > Vinod can you please post a complete compilable example? > > > > It is impossible to get anything done about your issue > > > > without stand alone test code. > > > > > > Ok, make sure you have 'device twa' in your kernel > > > configuration file, and apply these patches to > > > /sys/dev/twa/twa.c. > > > This patch causes the problem: > > > > "stand alone" means a single foo.c file that shows the problem > > you want fixed. > > I cannot submit a GCC bug report with a tarball of the entire > > FreeBSD kernel. > > I've taken the liberty to write up an example here. Not sure if > this is a bug or not: > > cc -O -pipe -c -fno-builtin -ffreestanding memset_bug.c > > Take a look at what is generated: > > objdump --disassemble memset_bug.o > > You'll see that instead of performing the inline code generation > for memset, the compiler generates a call to memset in the case of > the assignment of {0}. Have you tried -minline-all-stringops/-mno-inline-all-stringops? Jung-uk Kim