From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 49DC03858D28; Mon, 8 May 2023 19:37:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 49DC03858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683574642; bh=vbYPSIGhwV9DaNHdg/GETmJmZIBfyOzoKcTdMEpthxk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=O52KxVJleclwmncuSdH8bXJfjMi3e+V8PkObrtjNCl1rOwhCL7397ABZ6+CL99U8o 3SIOlbDZD6U3jfbsqPj2RQilMRtE9WF5h/v+KPsEvE52aQ109RZbpU7hGX8JM9RvcP bFFAd+0/e7HQNJ0oydQZkLx1HVHmG8Mx0Z6KCjbs= From: "law at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109777] [14 regression] Compare-debug failure after recent changes Date: Mon, 08 May 2023 19:37:22 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: compare-debug-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: law at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: priority Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109777 Jeffrey A. Law changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P4 --- Comment #4 from Jeffrey A. Law --- If it's inside the bfin bundling code, let's just mark it as a p4 and we can chase it down whenever it's convenient. My primary motivation is to catch generic issues. A target specific issue on a barely used target just isn't that interesting IMHO.=