From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3B7D03858D32; Fri, 3 Nov 2023 06:52:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3B7D03858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698994347; bh=GUgtZ0x31itNy5s7JrBkfG9wWMDrqcDEXCqESiZXFB0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kwnCVo0lMlZ+ctFHWsN2yXuUBYPUjbMjPzqaQRhxg0YsHvA5IzvxEuoOW0e8jHaLA mg2Pp+o9vyxFSWqJjXLboVEzEHJt7EMhPoducH23hCCb6MU3uWSHL1WTAo2P/HPYPE WzdSlIGgy2B/FsFvA/kuk/o0lV7YHlPXEtMpWFXo= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/109035] meaningless memory store on RISC-V and LoongArch Date: Fri, 03 Nov 2023 06:52:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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=3D109035 Xi Ruoyao changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #9 from Xi Ruoyao --- (In reply to Vladimir Makarov from comment #7) > For last 2 weeks I pushed several patches for better dealing with > equivalences in RA. >=20 > It seems the patches solves the current PR. I checked the test code > generation for loongarch and aarch64 and did not find spilled pseudos whi= ch > are reported here. >=20 > I think the PR should closed as fixed. Thanks! For LoongArch this issue has been "papered over" since r14-19 thou= gh it's a completely unrelated change. I'm closing the PR as fixed anyway.=