Date: Sun, 13 Jul 2003 07:21:19 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: kabaev@mail.ru Cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with <limits> Message-ID: <20030713.072119.61266976.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030713.072119.61266976.imp>