Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: tweak signed to unsigned local vars
Date: Mon, 12 Apr 2010 15:52:00 -0000	[thread overview]
Message-ID: <201004121150.49169.vapier@gentoo.org> (raw)
In-Reply-To: <20100412152413.GV19194@adacore.com>

[-- Attachment #1: Type: Text/Plain, Size: 2093 bytes --]

On Monday 12 April 2010 11:24:13 Joel Brobecker wrote:
> > diff --git a/sim/common/dv-sockser.c b/sim/common/dv-sockser.c
> > index 643ce34..18987f9 100644
> > --- a/sim/common/dv-sockser.c
> > +++ b/sim/common/dv-sockser.c
> > @@ -129,7 +129,8 @@ dv_sockser_init (SIM_DESC sd)
> > 
> >    struct sockaddr_in sockaddr;
> >    char hostname[100];
> >    const char *port_str;
> > 
> > -  int tmp,port;
> > +  unsigned tmp;
> > +  int port;
> 
> I'm not sure I agree on this one. "tmp" is used to store the result of
> a subtraction of 2 pointers. IIRC, the exact type returned is ptrdiff_t,
> which is a signed value...

true, but the math should never yield a negative value.  the compare is 
between a base pointer and a pointer returned from strchr() on the base 
pointer.  so the value should always be >= 0 and it should always fit in 
32bits.

> >  hw_port_encode (struct hw *me,
> >  
> >  		int port_number,
> >  		char *buf,
> > 
> > -		int sizeof_buf,
> > +		unsigned sizeof_buf,
> > 
> >  		port_direction direction)
> 
> Would type size_t work, in this case?

size_t would be usable in pretty much all the places i changed, but i 
consciously did not pick that because "unsigned" is the current convention, 
both with local vars and function arguments.  i didnt want to desync the type 
conventions where some used size_t and some used unsigned especially since 
they're different sizes on 64bit systems.

i certainly wouldnt be opposed to someone mass converting the source to 
size_t, but i dont think i'm going to volunteer for that ;)

> > @@ -583,7 +583,7 @@ hw_add_range_array_property (struct hw *me,
> > 
> >  			   * sizeof (unsigned_cell));
> >    
> >    unsigned_cell *cells = hw_zalloc (me, sizeof_cells);
> >    unsigned_cell *cell;
> > 
> > -  int i;
> > +  unsigned i;
> 
> I am not sure about this one either. Can you try changing the type
> of parameter nr_ranges to int? It looks like the only usage of this
> function is in hw-tree, and the variable used is actually an int...

i'll check these
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-04-12 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 21:58 Mike Frysinger
2010-04-12 15:24 ` Joel Brobecker
2010-04-12 15:52   ` Mike Frysinger [this message]
2010-04-12 16:06     ` Joel Brobecker
2010-04-12 18:30       ` Mike Frysinger
2010-04-12 19:59         ` Joel Brobecker
2010-04-12 18:45   ` Mike Frysinger

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=201004121150.49169.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=brobecker@adacore.com \
    --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