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 17:22:42 +0000 [thread overview] Message-ID: <bug-31181-4717-eKBJXzqfd4@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 #10 from Mike Frysinger <vapier at gentoo dot org> --- (In reply to Hans-Peter Nilsson from comment #9) > That last line seems superfluous and should yield errors. (Accidentally > quoted an untested diff?) yeah i didn't delete my partial comment ... already fixed it when i posted to the cgen mailing list > Beware that (IIRC) not > all compilers (old gcc, perhaps *cough* clang) support the same *location* > for the attribute (here, before the type). The canonical position is after; > "before the ';'". ok, easy enough to update > > + "CGEN_INSN_WORD insn = " > > (if (adata-integral-insn? CURRENT-ARCH) > > "entire_insn;\n" > > "base_insn;\n")) > > I don't know whether the "adata-integral-insn?" predicate has bearing on > whether insn can be "unused". Still: besides the superfluous line, I'd say > time to post it for review, with a link to this PR. i have no idea about adata-integral-insn here. i went with it because all the unused warnings are coming from insn=base_insn, not insn=entire_insn, and adata-integral-insn controls whether it's entire_insn or base_insn. i'll cc you on the v2 patch on the cgen list. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-21 17:22 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 2023-12-21 15:59 ` hp at sourceware dot org 2023-12-21 17:22 ` vapier at gentoo dot org [this message] 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-eKBJXzqfd4@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: linkBe 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).