From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: Randolph Chung <randolph@tausq.org>, gdb-patches@sources.redhat.com
Subject: Re: [patch/minor] fix compile warning in linux-proc.c
Date: Wed, 27 Aug 2003 04:25:00 -0000 [thread overview]
Message-ID: <3F4C32C3.7020504@redhat.com> (raw)
In-Reply-To: <yf2ad9xhedj.fsf@hawaii.kealia.com>
> On Wed, 20 Aug 2003 22:11:49 -0700, Randolph Chung <randolph@tausq.org> said:
>
>
>> While trying to get hppa-linux building with -Werror, I came across one
>> warning in linux-proc.c that's triggered by -Wformat-nonliteral. This
>> patch fixes it if anybody cares :)
>
>
> I'm seeing this on i686-pc-linux-gnu, too. The patch looks fine to me
> (though I'm not in a position to approve it); if I were in a
> hyper-refactoring mode, I suppose I'd be tempted to create new
> functions print_header_format_32, print_data_fmt_32,
> print_header_format_64, print_data_fmt_64 defined along these lines:
David, feel free to check it in. A comment mentioning that this should
use a generic (and not yet existing) local_address_string() method would
be useful.
The casts don't phase me. The conflicting "%#10lx" and "%#18lx" do but
again not desperatly. That local_address_string custom method.
Andrew
> static void
> print_data_fmt_64 (unsigned long addr, unsigned long endaddr,
> int size, unsigned int offset, const char *filename) {
> printf_filtered (" %#181x %#181x %#10x %#10x %7s\n",
> addr, endaddr, size, offset, filename);
> }
>
> but I don't think it's really urgent to do so. Hmm; maybe we really
> should do that, at least for the data strings, because it gets rid of
> casts? Andrew, what do you think?
next prev parent reply other threads:[~2003-08-27 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 5:08 Randolph Chung
2003-08-25 16:48 ` David Carlton
2003-08-27 4:25 ` Andrew Cagney [this message]
2003-08-27 15:42 ` David Carlton
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=3F4C32C3.7020504@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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