This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc Build Warnings

From: "Tom Browder" <tom dot browder at gmail dot com>
To: "Ian Lance Taylor" <iant at google dot com>
Cc: GCC-help <gcc-help at gcc dot gnu dot org>
Date: Mon, 29 Dec 2008 16:02:04 -0600
Subject: Re: gcc Build Warnings
References: <8bc817ee0812280611l30fe4afdva3d31e53bbb21244@mail.gmail.com> <m38wq0lzf3.fsf@google.com> <8bc817ee0812281759j582d817fmf684b96f017683db@mail.gmail.com> <m34p0mk6tk.fsf@google.com>

On Mon, Dec 29, 2008 at 3:30 PM, Ian Lance Taylor <iant@google.com> wrote:
...
> Sorry, I didn't quite understand your question.  In general we gcc
> developers don't want to suppress warnings that occur when building
> gcc.  In fact, during development we use -Werror, making all warnings
> be errors, so normally gcc builds with no warnings at all.  Of course,

I'll go back and redo my last build and look at the warnings, but I'm
pretty sure I see mostly the usual warnings about comparison of signed
versus unsigned and such that are probably due to developer
optimizations, but they are bothersome.

Thanks, Ian.

-Tom

Follow-Ups:
- Re: gcc Build Warnings
  - From: Ian Lance Taylor

References:
- gcc Build Warnings
  - From: Tom Browder
- Re: gcc Build Warnings
  - From: Ian Lance Taylor
- Re: gcc Build Warnings
  - From: Tom Browder
- Re: gcc Build Warnings
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]