public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyich@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: cgen@sourceware.org, Sergei Trofimovich <siarheit@google.com>
Subject: Re: [PATCH] cr16: fix build on gcc-12 (NULL comparison)
Date: Sun, 14 Nov 2021 18:34:14 +0000	[thread overview]
Message-ID: <20211114183400.31449948@nz> (raw)
In-Reply-To: <YZFR4nui9UZNGf3U@vapier>

On Sun, 14 Nov 2021 13:13:54 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> On 14 Nov 2021 17:42, Sergei Trofimovich via Cgen wrote:
> > From: Sergei Trofimovich <siarheit@google.com>
> > 
> > On gcc-12 build fails as:
> > 
> >     sim/cr16/interp.c: In function 'lookup_hash':
> >     sim/cr16/interp.c:89:25: error:
> >       the comparison will always evaluate as 'true'
> >       for the address of 'mnimonic' will never be NULL [-Werror=address]
> >        89 |   if ((h->ops->mnimonic != NULL) &&
> >           |                         ^~
> > 
> > 'mnimonic' is a sharr array within ops. It can never be NULL.
> > 
> > While at it renamed 'mnimonic' to 'mnemonic'.
> > ---
> >  sim/cr16/cr16_sim.h | 2 +-
> >  sim/cr16/interp.c   | 5 ++---
> >  2 files changed, 3 insertions(+), 4 deletions(-)  
> 
> this code doesn't exist in cgen.  did you mean to send the patch here ?
> -mike

My fault of not being able to read binutils-gdb/MAINTAINERS file.
I somehow read 'cgen/; cgen parts of opcodes/, sim/' as "all of sim/"
goes here.

Will resend to gdb-patches@sourceware.org.

Thank you!


-- 

  Sergei

      reply	other threads:[~2021-11-14 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14 17:42 Sergei Trofimovich
2021-11-14 18:13 ` Mike Frysinger
2021-11-14 18:34   ` Sergei Trofimovich [this message]

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=20211114183400.31449948@nz \
    --to=slyich@gmail.com \
    --cc=cgen@sourceware.org \
    --cc=siarheit@google.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).