Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Turn on -Werror by default
Date: Sun, 15 Jan 2006 17:01:00 -0000	[thread overview]
Message-ID: <20060115170103.GA5830@nevyn.them.org> (raw)
In-Reply-To: <200601082253.k08MrLY1000252@elgar.sibelius.xs4all.nl>

On Sun, Jan 08, 2006 at 11:53:21PM +0100, Mark Kettenis wrote:
> Sorry, but I think we've waited long enough.  GCC 4 has been out for 9
> months now, so people have had plenty of time to fix issues with it.
> In fact, I think people have largely ignored its problems because we
> don't enable -Werror by default.  I bet enabling it, will make people
> actually fix the problems.

What version of GCC are you using?  The first of 189 GCC 4 warnings in
my builds comes from source.c (and is a little non-obvious to fix, I'm
working on it).  Exactly one warning is in Linux-specific code.

I definitely object if you're going to check in a patch that makes GDB
build nowhere by default.

> If you're talking about Linux builds that fall over with -Werror even
> with older GCC versions, then there is no real excuse.  GDB
> maintainers should have been compiling with -Werror for at least the
> past four years.

FYI, most of the -Werror problems in Linux builds with older compilers
are specifically fallout of fixes for the stupid GCC 4 warnings.  It
_used_ to build with -Werror until mass interface changes started
breaking it.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-01-15 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 17:59 Mark Kettenis
2006-01-08 22:25 ` Daniel Jacobowitz
2006-01-08 22:53   ` Mark Kettenis
2006-01-15 17:01     ` Daniel Jacobowitz [this message]
2006-01-15 17:56       ` Mark Kettenis
2006-01-15 18:21         ` Daniel Jacobowitz
2006-01-15 20:04           ` Mark Kettenis
2006-01-15 20:26             ` Daniel Jacobowitz
2006-01-15 20:40               ` Mark Kettenis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060115170103.GA5830@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox