Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [ob] More warnings; Call for assistance
Date: Tue, 17 Jan 2006 20:23:00 -0000	[thread overview]
Message-ID: <20060117202323.GA11359@nevyn.them.org> (raw)
In-Reply-To: <u1wz68vc0.fsf@gnu.org>

On Tue, Jan 17, 2006 at 10:15:27PM +0200, Eli Zaretskii wrote:
> > Date: Tue, 17 Jan 2006 10:17:31 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > /space/fsf/commit/src/gdb/expprint.c:180: warning: pointer targets in passing argument 2 of 'current_language->la_printstr' differ in signedness
> 
> Is it really worth your trouble fixing this?  AFAIK, the next release
> of GCC is supposed to turn this warning off by default, so why fix
> something that ain't broken in the first place, if it's gonna bug only
> those users who have GCC 4.0.x?

Do you have a reference for this GCC change?

Also, do you think the warning is useless?  If you think it's useless,
I'll just stop, and we'll go with Mark's patch to disable it.

-- 
Daniel Jacobowitz
CodeSourcery


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 15:17 Daniel Jacobowitz
2006-01-17 15:22 ` Daniel Jacobowitz
2006-01-17 19:37   ` Jim Blandy
2006-01-17 19:46     ` Daniel Jacobowitz
2006-01-17 20:11       ` Eli Zaretskii
2006-01-20 23:06         ` Daniel Jacobowitz
2006-01-21 10:07           ` Eli Zaretskii
2006-01-21 15:18             ` Daniel Jacobowitz
2006-01-17 20:57       ` Jim Blandy
2006-01-17 20:17     ` Eli Zaretskii
2006-01-20 23:09   ` Daniel Jacobowitz
2006-01-17 20:19 ` Eli Zaretskii
2006-01-17 20:23   ` Daniel Jacobowitz [this message]
2006-01-17 21:08     ` Eli Zaretskii
2006-01-17 21:14       ` Daniel Jacobowitz
2006-01-18  4:16         ` Eli Zaretskii
2006-01-18  1:15 ` Jim Blandy
2006-01-18 23:33   ` Daniel Jacobowitz

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=20060117202323.GA11359@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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