From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Fwd: -Wpointer-sign for GCC 4.1
Date: Wed, 18 Jan 2006 23:59:00 -0000 [thread overview]
Message-ID: <20060118231948.GA19079@nevyn.them.org> (raw)
In-Reply-To: <200601182224.k0IMO9Y7030185@elgar.sibelius.xs4all.nl>
On Wed, Jan 18, 2006 at 11:24:09PM +0100, Mark Kettenis wrote:
> Let's forget about them. The mostly bogus signed vs. unsigned char
> ones dominate the useful warnings for the other integers.
>
> Is there any reason not to commit my -Werror patch now (with the
> -Wno-pointer-sign)?
It's fine with me, but I'd like to make sure Jim agrees first; I'm not
sure if he's said or not.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-18 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060117211914.GA13055@nevyn.them.org>
[not found] ` <39BD9F7D-F512-40EA-804A-DBE9BAC97E2B@apple.com>
[not found] ` <20060118173155.GM28863@synopsys.com>
2006-01-18 18:44 ` Jim Blandy
2006-01-18 18:59 ` Daniel Jacobowitz
2006-01-18 19:01 ` Jim Blandy
2006-01-18 19:26 ` Daniel Jacobowitz
2006-01-18 20:29 ` Eli Zaretskii
2006-01-18 23:18 ` Mark Kettenis
2006-01-18 23:59 ` Daniel Jacobowitz [this message]
2006-01-19 1:01 ` Jim Blandy
2006-01-19 16:52 ` Eli Zaretskii
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=20060118231948.GA19079@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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