Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: ppc: fix some Wpointer-sign warnings
Date: Wed, 19 May 2021 12:32:02 -0400	[thread overview]
Message-ID: <YKU9gkJQzwr2ydJm@vapier> (raw)
In-Reply-To: <20210519104646.GA11845@delia>

On 19 May 2021 12:46, Tom de Vries wrote:
> --- a/sim/ppc/hw_memory.c
> +++ b/sim/ppc/hw_memory.c
> @@ -190,7 +190,7 @@ hw_memory_init_address(device *me)
>    if (device_find_property(me, "available") != NULL) {
>      hw_memory_chunk **curr_chunk = &hw_memory->heap;
>      int cell_nr;
> -    unsigned_cell dummy;
> +    signed_cell dummy;
>      int nr_cells = device_find_integer_array_property(me, "available", 0, &dummy);

this one is fine

> @@ -199,9 +199,9 @@ hw_memory_init_address(device *me)
>  	 cell_nr += 2) {
>        hw_memory_chunk *new_chunk = ZALLOC(hw_memory_chunk);
>        device_find_integer_array_property(me, "available", cell_nr,
> -					 &new_chunk->address);
> +					 (signed_cell *)&new_chunk->address);
>        device_find_integer_array_property(me, "available", cell_nr + 1,
> -					 &new_chunk->size);
> +					 (signed_cell *)&new_chunk->size);
> 
> --- a/sim/ppc/hw_opic.c
> +++ b/sim/ppc/hw_opic.c
> @@ -417,10 +417,12 @@ hw_opic_init_data(device *me)
>        }
>        if (!device_find_integer_array_property(me, "interrupt-ranges",
>  					      reg_nr * 2,
> -					      &opic->isu_block[isb].int_number)
> +					      (signed_cell *)
> +					        &opic->isu_block[isb].int_number)
>  	  || !device_find_integer_array_property(me, "interrupt-ranges",
>  						 reg_nr * 2 + 1,
> -						 &opic->isu_block[isb].range))
> +						 (signed_cell *)
> +						   &opic->isu_block[isb].range))

these ones i'm not sure about.  it does fix the warnings, and it doesn't
change the status quo behavior, but i don't think it's the actual fix we
would want.  if the device tree has a negative number, it'll get converted
to an unsigned number.  i haven't thought hard as to what the right fix
would look like here.

i think we'd have to look at what other device tree users are doing like
in boot loaders (e.g. u-boot) and in the linux kernel.
-mike

  reply	other threads:[~2021-05-19 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 10:46 Tom de Vries
2021-05-19 16:32 ` Mike Frysinger via Gdb-patches [this message]
2021-05-20 11:59   ` Tom de Vries
2021-05-20 12:08   ` Tom de Vries
2021-09-09  3:17   ` Mike Frysinger via Gdb-patches

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=YKU9gkJQzwr2ydJm@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=vapier@gentoo.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