From owner-freebsd-current@FreeBSD.ORG  Fri Jul 18 18:25:36 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 587B337B401; Fri, 18 Jul 2003 18:25:36 -0700 (PDT)
Received: from lifesupport.shutdown.com (dsl092-048-059.sfo2.dsl.speakeasy.net
	[66.92.48.59])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B474F43FBD; Fri, 18 Jul 2003 18:25:35 -0700 (PDT)
	(envelope-from llewelly@lifesupport.shutdown.com)
Received: (from llewelly@localhost)
	by lifesupport.shutdown.com (8.11.2/8.11.2) id h6J1LCH07167;
	Fri, 18 Jul 2003 18:21:12 -0700 (PDT)
To: Nate Lawson <nate@root.org>
References: <20030718121511.I26395@root.org>
From: LLeweLLyn Reese <llewelly@lifesupport.shutdown.com>
Date: 18 Jul 2003 18:21:11 -0700
In-Reply-To: <20030718121511.I26395@root.org>
Message-ID: <x3oezrnwfs.fsf@lifesupport.shutdown.com>
Lines: 25
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: kan@freebsd.org
cc: current@freebsd.org
Subject: Re: warning: inlining failed
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jul 2003 01:25:36 -0000

Nate Lawson <nate@root.org> writes:

> Warner mentioned this was due to the gcc import.  Nearly every part of the
> kernel that uses newbus or buf.h prints out lots of warnings.  Can someone
> see about fixing this, whether it's by fixing our headers or build flags
> or gcc itself?  I've already wasted a few reboot cycles because valid
> warnings were lost in the crowd.
> 
> cc -O -pipe -mcpu=pentiumpro  -D_KERNEL -Wall -Wredundant-decls
> -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
> -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -std=c99
> -DKLD_MODULE -nostdinc -I-   -I. -I@ -I@/dev -I@/../include
> -I/usr/include -fno-common  -mno-align-long-strings
> -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls
> -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
> -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -std=c99
> -c
[snip]

-Wno-inline will disable warnings about functions not getting
    inlined. If the inlining is necessary, consider -finline-limit as
    suggested by another poster.

I haven't tried it myself, but it seems probably harmless and at least
    useful for seeing those other warnings you'd like to see.