From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D82123858C56; Wed, 6 Dec 2023 18:32:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D82123858C56 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701887560; bh=OhHcdZDtWws5XJ0OYU5selUetqLiIlbbNlpByT5lYeU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xnv4HPiVQYLE55H2cc+fLf63LFdtEIwTBSqNXhkF9MHCkOXUEPArxIgdhXAQYlsmZ ezDv2JceB798aQE3ur+hMmMgYPeNK/mlZ5Z84GADrYAlYniZI/nxP6KTlytsrk3qut 1qSfijEjtY/7tOwiZnalXofiGe+a17DWypRzTMrs= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112572] [14 regression] LLVM miscompiled since r14-5355-g3cd3a09b3f91a1 Date: Wed, 06 Dec 2023 18:32:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: blocker X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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=3D112572 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #34 from Andrew Pinski --- (In reply to Jakub Jelinek from comment #33) > This should be now hopefully latent after > r14-6210-ge44ed92dbbe9d4e5c23f486cd2f77a6f9ee513c5, we need to decide abo= ut > the updating and usability of REG_UNUSED notes, but after moving the pass= it > shouldn't trigger on this testcase. Which case this becomes a dup of bug 40209 which is tracking the single_set usage issue (and has for a long time). *** This bug has been marked as a duplicate of bug 40209 ***=