From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Fwd: -Wpointer-sign for GCC 4.1
Date: Wed, 18 Jan 2006 19:26:00 -0000 [thread overview]
Message-ID: <20060118190120.GA11089@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0601181058r23b810dg9d926e40f07d0704@mail.gmail.com>
On Wed, Jan 18, 2006 at 10:58:59AM -0800, Jim Blandy wrote:
> On 1/18/06, Daniel Jacobowitz <drow@false.org> wrote:
> > On Wed, Jan 18, 2006 at 10:40:55AM -0800, Jim Blandy wrote:
> > > The message below is kind of odd. We do use -Wall
> >
> > No, we don't. See the comments in configure.ac about this.
>
> D'oh. You're right, of course.
>
> > Sorry, that wasn't my goal. My goal with forwarding this to the GCC
> > list was independent of what GDB should do - as Joe wrote, the GCC SC
> > made a promise to RMS that I'm trying to make sure doesn't slip through
> > the cracks.
>
> Okay. I'd gotten the impression from your conversation with Eli that
> the plan was to just forget the whole thing if future GCC's were going
> to drop the warning.
Nah - my plan is to forget the whole thing if we decide to, but no one
wants to decide.
You and I and a couple of others in the past have squashed most of
these warnings in GDB. At the moment I'm not convinced that running
around hammering on the rest of them is a worthwhile use of our time,
though.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-18 19:01 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 [this message]
2006-01-18 20:29 ` Eli Zaretskii
2006-01-18 23:18 ` Mark Kettenis
2006-01-18 23:59 ` Daniel Jacobowitz
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=20060118190120.GA11089@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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