Date: 18 Jul 2003 18:38:31 -0700 From: LLeweLLyn Reese <llewelly@lifesupport.shutdown.com> To: Alexander Kabaev <kan@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: gcc-3.3 issues Message-ID: <x3he5jnvmw.fsf@lifesupport.shutdown.com> In-Reply-To: <20030718190420.GA84963@freefall.freebsd.org> References: <20030718190420.GA84963@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?x3he5jnvmw.fsf>