Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] remote-e7000.c warnings
Date: Wed, 11 Jul 2001 19:42:00 -0000	[thread overview]
Message-ID: <3B4D0EA3.6050001@cygnus.com> (raw)
In-Reply-To: <15180.65506.552976.660043@krustylu.cygnus.com>

> This patch removes warnings when building remote-e7000.c.  (On Linux
> 7.0) Since this file gets build with target=sh-elf, I was getting
> tired of all the warnings on the screen.
> But then I saw the FIXME in the Makefile, so I am not sure what to do.



> # FIXME: For the SH target, remote-e7000 contains numerous -Wformat
> # warnings.  Since the fixes involve modifications to the code that
> # handles the SH remote protocol the changes need to be tested against
> # an SH board before they can be committed. cagney 1999-09-01.


This is me be paranoid :-)  If you can find someone to test it then 
good, if not, we might as well just bite the bullet and let it go in 
anway :-/  It certainly falls under:

``All maintainers can make mechanical (params, spelling, indentation,
multi-arch, -W..., ....) changes to ``maintenance only'' targets.
Please sanity check the change by compiling with one of the listed
targets.''


> -	  sprintf (buf, ".ER%d %lx\r", regno, read_register (regno));
> +	  sprintf (buf, ".ER%d %lx\r", regno, (long) read_register (regno));


To think out loud, is:

	sprintf (buf, ".ER%d %s\r", regno, phex_nz (read_register (regno), 0);

more portable?  I suspect I had that in mind and hence the comment.

	enjoy,
		Andrew


  reply	other threads:[~2001-07-11 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 18:32 Elena Zannoni
2001-07-11 19:42 ` Andrew Cagney [this message]
2001-07-13 13:04   ` Elena Zannoni

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=3B4D0EA3.6050001@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    /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