From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32724 invoked by alias); 4 Jun 2010 16:37:14 -0000 Received: (qmail 32632 invoked by uid 48); 4 Jun 2010 16:36:57 -0000 Date: Fri, 04 Jun 2010 16:37:00 -0000 Message-ID: <20100604163657.32631.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug bootstrap/44307] do not enable warnings when building with the host compiler In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "manu at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-06/txt/msg00501.txt.bz2 ------- Comment #8 from manu at gcc dot gnu dot org 2010-06-04 16:36 ------- -Wuninitialized is enabled by -Wall (or perhaps -Wextra), not explicitly. I think we should not enable any warnings when building with the host compiler, unless the user requests them. It is probably faster and would produce less clutter in the output. But I don't have enough time to provide a patch to fix this, and I doubt any main developer considers this a priority. -- manu at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Component|middle-end |bootstrap Resolution|WONTFIX | Summary|warning: may be used |do not enable warnings when |uninitialized in this |building with the host |function often building gcc |compiler http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44307