Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/6] sim: sh: rework register layout with anonymous unions & structs
Date: Thu, 11 Nov 2021 17:25:44 -0500	[thread overview]
Message-ID: <YY2YaL+rjKkIBBig@vapier> (raw)
In-Reply-To: <68a4c7ee-700a-22f5-62ad-9257de03e9f9@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

On 11 Nov 2021 09:41, Luis Machado wrote:
> I can't pinpoint the exact SH patch, but builds are broken for 
> --enable-targets=all in Ubuntu 18.04 with GCC 7.5:

pretty sure the warnings have always been there for you, we just turned
-Werror in more cases recently

> binutils-gdb/sim/sh/interp.c: In function ‘ppi_insn’:
> ./ppi.c:875:21: error: assuming signed overflow does not occur when 
> assuming that (X + c) < X is always false [-Werror=strict-overflow]
>           carry = res < Sy;
>                   ~~~~^~~~
> ./ppi.c:849:21: error: assuming signed overflow does not occur when 
> assuming that (X - c) > X is always false [-Werror=strict-overflow]
>           carry = res > Sy;
>                   ~~~~^~~~
> ./ppi.c:823:21: error: assuming signed overflow does not occur when 
> assuming that (X + c) < X is always false [-Werror=strict-overflow]
>           carry = res < Sx;
>                   ~~~~^~~~
> ./ppi.c:797:21: error: assuming signed overflow does not occur when 
> assuming that (X - c) > X is always false [-Werror=strict-overflow]
>           carry = res > Sx;
>                   ~~~~^~~~
> binutils-gdb-arm64-bionic/sim/../../../repos/binutils-gdb/sim/sh/interp.c: 
> In function ‘sim_resume’:
> ./ppi.c:1178:28: warning: ‘res’ may be used uninitialized in this 
> function [-Wmaybe-uninitialized]
>             MACL = DSP_R (z) = res;
> ./ppi.c:44:7: note: ‘res’ was declared here
>     int res, res_grd;
>         ^~~

how exactly are you building things ?  we don't enable -Wstrict-overflow.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-11-11 22:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07  0:32 Mike Frysinger via Gdb-patches
2021-11-07  0:32 ` [PATCH 2/6] sim: sh: fix unused-value warnings Mike Frysinger via Gdb-patches
2021-11-07  0:32 ` [PATCH 3/6] sim: sh: fix various parentheses warnings Mike Frysinger via Gdb-patches
2021-11-07  0:32 ` [PATCH 4/6] sim: sh: constify a few read-only lookup tables Mike Frysinger via Gdb-patches
2021-11-07  0:32 ` [PATCH 5/6] sim: sh: fix uninitialized variable usage with pdmsb Mike Frysinger via Gdb-patches
2021-11-07  0:32 ` [PATCH 6/6] sim: sh: enable -Werror everywhere Mike Frysinger via Gdb-patches
2021-11-11 12:41 ` [PATCH 1/6] sim: sh: rework register layout with anonymous unions & structs Luis Machado via Gdb-patches
2021-11-11 22:25   ` Mike Frysinger via Gdb-patches [this message]
2021-11-11 22:32     ` Luis Machado via Gdb-patches
2021-11-11 22:38       ` Luis Machado via Gdb-patches
2021-11-11 22:45       ` Mike Frysinger via Gdb-patches
2021-11-12 13:12         ` Luis Machado via Gdb-patches
2021-11-12  0:39   ` [PATCH 1/2] sim: sh: rework carry checks to not rely on integer overflows Mike Frysinger via Gdb-patches
2021-11-12  0:39     ` [PATCH 2/2] sim: sh: fix switch-bool warnings 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=YY2YaL+rjKkIBBig@vapier \
    --to=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --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