From owner-freebsd-current@FreeBSD.ORG  Fri Jul 18 18:42:56 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 6C55F37B401; Fri, 18 Jul 2003 18:42:56 -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 9662C43FB1; Fri, 18 Jul 2003 18:42:55 -0700 (PDT)
	(envelope-from llewelly@lifesupport.shutdown.com)
Received: (from llewelly@localhost)
	by lifesupport.shutdown.com (8.11.2/8.11.2) id h6J1cWF07215;
	Fri, 18 Jul 2003 18:38:32 -0700 (PDT)
To: Alexander Kabaev <kan@FreeBSD.org>
References: <20030718190420.GA84963@freefall.freebsd.org>
From: LLeweLLyn Reese <llewelly@lifesupport.shutdown.com>
Date: 18 Jul 2003 18:38:31 -0700
In-Reply-To: <20030718190420.GA84963@freefall.freebsd.org>
Message-ID: <x3he5jnvmw.fsf@lifesupport.shutdown.com>
Lines: 21
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: "Jacques A. Vidrine" <nectar@FreeBSD.org>
cc: freebsd-current@FreeBSD.org
Subject: Re: gcc-3.3 issues
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:42:56 -0000

Alexander Kabaev <kan@FreeBSD.org> writes:

> > [snip]
> >
> > Curiosity: Why does this suppression get disabled in the imported compiler?
> 
> I guess justification was to see warnings about FreeBSD's own header
> files. We dont want to hide warnings in them, we want to fix issues
> warnings report.

Ok. This makes sense. However, if these warnings are disguising more
    important warnings in some ports, may I suggest people looking to
    fix warnings in those ports try compiling with -Wno-system-headers,
    which I believe will disable the warnings from gcc's headers. Of
    course anyone looking to fix warnings in headers should leave
    -Wsystem-headers on.

> C++ headers just a side effect of that decision.

I guess this is evidence that #pragma GCC system_header isn't
    quite enough. :-)