From owner-freebsd-current@FreeBSD.ORG  Sun Jul 13 06:22:10 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 437CB37B401
	for <freebsd-current@freebsd.org>;
	Sun, 13 Jul 2003 06:22:10 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8094243FAF
	for <freebsd-current@freebsd.org>;
	Sun, 13 Jul 2003 06:22:09 -0700 (PDT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.8/8.12.3) with ESMTP id h6DDLxJm079554;
	Sun, 13 Jul 2003 07:21:59 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Sun, 13 Jul 2003 07:21:19 -0600 (MDT)
Message-Id: <20030713.072119.61266976.imp@bsdimp.com>
To: kabaev@mail.ru
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030713000559.28c18be6.kabaev@mail.ru>
References: <BEDC8C48-B4DC-11D7-BE3B-0003937E39E0@mac.com>
	<20030713031312.GA89014@crodrigues.org>
	<20030713000559.28c18be6.kabaev@mail.ru>
X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: rodrigc@crodrigues.org
cc: freebsd-current@freebsd.org
Subject: Re: GCC 3.3.1, new warnings with <limits>
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: Sun, 13 Jul 2003 13:22:10 -0000

In message: <20030713000559.28c18be6.kabaev@mail.ru>
            Alexander Kabaev <kabaev@mail.ru> writes:
: Short of fixing offending files in FSF libstdc++ or turning warning
: suppression back on for standard C++ include files selectively, I have
: no suggestion.

In the past I know that FSF has accepted patches back, so maybe the
right thing to do is:

o figure out the fix(es) that we need.
o submit them to fsf
o if they accpet them, then we can import them on the vendor branch
  or
  disable warnings in the system headers if not

The warnings are quite annoying, and we'll get a lot of grief from the
growing number of large c++ ports.  I'd be happy to come up with a
patch.

Warner