From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F41D53858439; Wed, 20 Dec 2023 03:19:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F41D53858439 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1703042345; bh=A3j1ATB98Fu6GQiK2tAHZEirexeM2NYbkUNiQhau7rs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kuEke1yTEtwWxdOu24SUikl77VVH0mPAP3dKtRZ/apworcC5zt11h8k4q34utP+Hl t2upsyuXRxOAX+YQN48oYt/Jr+CXAPJ97BnImESSX5dNLEH+rct324GihiuuMdpl0Q SvuS7YsWNEvrQaRefeGJR6ehRgoAcJTCsKWCgVis= From: "vapier at gentoo dot org" To: gdb-prs@sourceware.org Subject: [Bug sim/31181] sim: cris: decode unused base_insn variable warnings Date: Wed, 20 Dec 2023 03:19:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: sim X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vapier at gentoo dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31181 --- Comment #4 from Mike Frysinger --- (In reply to Hans-Peter Nilsson from comment #3) > My point is that *these two files* would be the only files that got > -Wno-error=3Dunused-variable. i understand what you're suggesting. my point still stands. this assumes = that the toolchain used to compile the sim recognizes & accepts (or silently ignores) "-Wno-error=3Dunused-variable". the sim, like all binutils+gdb projects, test the toolchain and whether it supports -W flags before using them. we have to add a test for -Wno-error=3Dunused-variable, a variable f= or it, and then expand that for these 2 files. seems a lot easier to fix the orig= in, especially when enabling warnings has a proven history of uncovering real b= ugs. > You say, you've looked for, but not found, a > bug-reason why the warnings appear, in this generated code, presumably > including looking at the generator. the generator appears to be cgen lisp which uses the lisp cpu definitions. = the cgen code is not easy to follow at all, or trace back which funcs generate which lines. i was hoping you, as author of much of this code, would be ab= le to pick out & fix things much quicker than i. --=20 You are receiving this mail because: You are on the CC list for the bug.=