From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Cc: "'Corinna Vinschen'" <vinschen@redhat.com>
Subject: RE: [RFA] ARI fix: Remove OP at end of line in xstormy16-tdep.c
Date: Tue, 19 Apr 2011 12:41:00 -0000 [thread overview]
Message-ID: <007e01cbfe8f$0f9e4480$2edacd80$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201104191208.01363.pedro@codesourcery.com>
Thank you for the suggestion, this makes the things
cleaner.
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : mardi 19 avril 2011 13:08
> À : gdb-patches@sourceware.org
> Cc : Pierre Muller
> Objet : Re: [RFA] ARI fix: Remove OP at end of line in xstormy16-tdep.c
>
> On Tuesday 19 April 2011 11:41:34, Pierre Muller wrote:
> > --- xstormy16-tdep.c 18 Mar 2011 18:52:32 -0000 1.114
> > +++ xstormy16-tdep.c 19 Apr 2011 10:35:47 -0000
> > @@ -264,11 +264,9 @@ xstormy16_push_dummy_call (struct gdbarc
> > val = value_contents (args[i]);
> > for (j = 0; j < typelen; j += xstormy16_reg_size)
> > regcache_cooked_write_unsigned (regcache, argreg++,
> > - extract_unsigned_integer (val + j,
> > - typelen - j ==
> > - 1 ? 1 :
> > - xstormy16_reg_size,
> > - byte_order));
> > + extract_unsigned_integer (val + j,
> > + typelen - j == 1 ? 1 :
> > xstormy16_reg_size,
> > + byte_order));
>
> A sign that temporary variables would help, IMO:
>
> for (j = 0; j < typelen; j += xstormy16_reg_size)
> {
> ULONGEST regval;
> int size;
>
> size = typelen - j == 1 ? 1 : xstormy16_reg_size;
> val = extract_unsigned_integer (val + j, size, byte_order);
> regcache_cooked_write_unsigned (regcache, argreg++, regval);
> );
So here is the new proposal:
Corinna, you are listed as maintainer of
xstormy16-tdep, could you tell if this is OK?
Pierre Muller
2011-04-19 Pierre Muller <muller@ics.u-strasbg.fr>
Pedro Alves <pedro@codesourcery.com>
* xstormy16-tdep.c (xstormy16_push_dummy_call): Add local
variables to simplify code and avoid == operator at end of
line as this is against GNU coding standards.
Index: xstormy16-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/xstormy16-tdep.c,v
retrieving revision 1.114
diff -u -p -r1.114 xstormy16-tdep.c
--- xstormy16-tdep.c 18 Mar 2011 18:52:32 -0000 1.114
+++ xstormy16-tdep.c 19 Apr 2011 12:34:34 -0000
@@ -263,12 +263,13 @@ xstormy16_push_dummy_call (struct gdbarc
/* Put argument into registers wordwise. */
val = value_contents (args[i]);
for (j = 0; j < typelen; j += xstormy16_reg_size)
- regcache_cooked_write_unsigned (regcache, argreg++,
- extract_unsigned_integer (val + j,
- typelen - j ==
- 1 ? 1 :
- xstormy16_reg_size,
- byte_order));
+ {
+ ULONGEST regval;
+ int size = (typelen -j == 1) ? 1 : xstormy16_reg_size;
+
+ regval = extract_unsigned_integer (val + j, size, byte_order);
+ regcache_cooked_write_unsigned (regcache, argreg++, regval);
+ }
}
/* Align SP */
next prev parent reply other threads:[~2011-04-19 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 10:41 Pierre Muller
2011-04-19 11:08 ` Pedro Alves
2011-04-19 12:41 ` Pierre Muller [this message]
2011-04-19 12:52 ` Corinna Vinschen
2011-04-19 12:58 ` Pierre Muller
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='007e01cbfe8f$0f9e4480$2edacd80$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=vinschen@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