public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/31181] sim: cris: decode unused base_insn variable warnings
Date: Thu, 21 Dec 2023 04:12:49 +0000	[thread overview]
Message-ID: <bug-31181-4717-jaCvGO8bME@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31181-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31181

--- Comment #8 from Mike Frysinger <vapier at gentoo dot org> ---
(In reply to Hans-Peter Nilsson from comment #5)
> I don't think that's necessary: warnings are only enabled for gcc

they're enabled for toolchains that define __GNUC__.  llvm is known to do this
too.  i don't know the current status, but Intel's ICC has done this in the
past.  neither of those are gcc, and i don't like our build binding to CLI
behavior.

> Nah, that seems a bit overthinking it.  Adding it when warnings are enabled
> should be sufficient.  Alternatively, we can just add a "-Wno-error" like
> the extant cases.

-Wno-error makes it even easier for things to slip in.  there are plenty of
examples of this across software projects, including the sim.

> Developers can be expected to have a sufficiently modern gcc
> ...
> I don't have a new enough gcc to emit those particular ones

one person's modern is another's too-old ;)

> But, for that kind of change, this PR should be redirected to that project,
> as the template is there, in cgen/sim-decode.scm according to git grep.

sure, if we think the right place is cgen, i can send it there.  i wasn't sure
if it was something we'd do entirely there, or if we'd change cpu/cris.cpu, or
both.

ideally there would be something in the cpu definition that cgen could key of
off (like the arguments passed down, or what implicitly requested more fields
be decoded, or something else).  if that's not feasible, then i'd go with:

--- a/sim-decode.scm
+++ b/sim-decode.scm
@@ -436,7 +436,14 @@ void
    "    const IDESC *idesc = &" IDESC-TABLE-VAR "[itype];\n"
    (if (> (length (sfmt-iflds sfmt)) 0)
        (string-append
-        "    CGEN_INSN_WORD insn = "
+        "    "
+        ; Some insns are fully decoded by the time they get here, so they
won't
+        ; access the insn variable.  Mark it as unused to avoid warnings.
+        and don't need the i
+        (if (adata-integral-insn? CURRENT-ARCH)
+            ""
+            "ATTRIBUTE_UNUSED ")
+        "CGEN_INSN_WORD insn = "
         (if (adata-integral-insn? CURRENT-ARCH)
             "entire_insn;\n"
             "base_insn;\n"))

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-12-21  4:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  2:34 [Bug sim/31181] New: " vapier at gentoo dot org
2023-12-19  3:13 ` [Bug sim/31181] " hp at sourceware dot org
2023-12-19 10:09 ` vapier at gentoo dot org
2023-12-19 23:35 ` hp at sourceware dot org
2023-12-20  3:19 ` vapier at gentoo dot org
2023-12-20 15:58 ` hp at sourceware dot org
2023-12-21  1:10 ` tromey at sourceware dot org
2023-12-21  1:50 ` hp at sourceware dot org
2023-12-21  4:12 ` vapier at gentoo dot org [this message]
2023-12-21 15:59 ` hp at sourceware dot org
2023-12-21 17:22 ` vapier at gentoo dot org
2023-12-21 17:32 ` hp at sourceware dot org
2023-12-21 17:41 ` hp at sourceware dot org
2023-12-22  1:19 ` vapier at gentoo dot org
2023-12-22 15:47 ` vapier at gentoo dot org

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=bug-31181-4717-jaCvGO8bME@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).