public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new toolchain snapshots
Date: Thu, 31 Aug 2000 20:23:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205434@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205422@msgid-missing>

>>>>> On Thu, 31 Aug 2000 13:08:07 -0700, Jim Wilson <wilson@cygnus.com> said:

  Jim> 	I'm getting a lot of warnings for format %p with the new
  Jim> toolchain on kernel 2.4.0-test7, e.g.

  Jim> Before everyone goes and changes a lot of code, you should be
  Jim> aware that these warnings have since changed several times in
  Jim> the FSF gcc sources.  And will likely change again in the
  Jim> future.

  Jim> The current FSF gcc sources won't give a warning for void * or
  Jim> char * used with %p, and will accept other pointer types if you
  Jim> aren't using -pedantic.

  Jim> We can either live with the current set of warnings, or I can
  Jim> try to bring over patches from more recent FSF gcc sources to
  Jim> make them go away.

OK, sounds good.

I should say that this issue bothers me much less than those stupid
"format is not a string constant" messages.  The reason I hate those
messages is because this is the only place gcc gives a warning without
there being a way to get rid of it.  I don't think this warning should
be turned on for -Wall.

	--david

PS: Yeah, I realize that I'm probably barking up the wrong tree.... ;-)


  parent reply	other threads:[~2000-08-31 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30 23:54 [Linux-ia64] new toolchain snapshots Jim Wilson
2000-08-31  7:12 ` Keith Owens
2000-08-31 12:44 ` Dan Pop
2000-08-31 17:43 ` David Mosberger
2000-08-31 20:08 ` Jim Wilson
2000-08-31 20:23 ` David Mosberger [this message]
2000-08-31 22:19 ` Jim Wilson
2000-08-31 22:29 ` David Mosberger
2000-09-01  4:49 ` Keith Owens
2000-09-02  3:01 ` Jim Wilson
2000-09-02  4:00 ` Keith Owens

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=marc-linux-ia64-105590678205434@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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