From owner-freebsd-sparc64@FreeBSD.ORG Thu Feb 2 08:32:57 2006 Return-Path: X-Original-To: sparc64@FreeBSD.org Delivered-To: freebsd-sparc64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7324416A422; Thu, 2 Feb 2006 08:32:57 +0000 (GMT) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1155A43D46; Thu, 2 Feb 2006 08:32:54 +0000 (GMT) (envelope-from mj@feral.com) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.4/8.13.4) with ESMTP id k128Wpah083573; Thu, 2 Feb 2006 00:32:51 -0800 (PST) (envelope-from mj@feral.com) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.4/8.13.4/Submit) with ESMTP id k128WmOD083570; Thu, 2 Feb 2006 00:32:50 -0800 (PST) (envelope-from mj@feral.com) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Thu, 2 Feb 2006 00:32:48 -0800 (PST) From: Matthew Jacob X-X-Sender: mjacob@ns1.feral.com To: Scott Long In-Reply-To: <86fyn242w0.fsf@xps.des.no> Message-ID: <20060202002644.M82118@ns1.feral.com> References: <20060201165326.6E44E7302F@freebsd-current.sentex.ca> <20060201180223.O52964@beagle.kn.op.dlr.de> <43E0F41C.5020907@samsco.org> <86fyn242w0.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-604823647-1138869168=:82118" Cc: stable@FreeBSD.org, src-committers@FreeBSD.org, Harti Brandt , sparc64@FreeBSD.org Subject: Re: [releng_6 tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthew Jacob List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2006 08:32:57 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-604823647-1138869168=:82118 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Hmm- I doesn't recall "name not mentioned" telling me about this earlier- perhaps he can dig up the mail as I haven't had any mail from him directly in years that I recall. Is the tinderbox still failing? I haven't seen that mail- maybe I'm not on the list it's being sent to? There are two complaints by the sparc64 complier- now that somebody (Marius) gave me useful information I will address it when I have a spare moment tomorrow. Insofar as inlining is concern- possibly so, but it demonstrably causes no compiler complaints in about 50 other contexts. My main concern at the moment is to make sure that the tinderbox failures are addressed and to pretty much ignore anything else from "name not mentioned". On Thu, 2 Feb 2006, Dag-Erling Smørgrav wrote: > Scott Long writes: >> I've been trying to reproduce this on my local hardware, but I can't >> trigger it. > > The ISP driver abuses the inline keyword. As I told mjacob earlier, > the extensive inlining not only breaks the build, but probably hurts > performance as well. > > (what gcc is complaining about, specifically, is that expanding calls > to inlined functions causes isp_target_notify() to grow by more than > 100%) > > DES > -- > Dag-Erling Smørgrav - des@des.no > > --0-604823647-1138869168=:82118--