From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C19443861001; Wed, 10 Apr 2024 14:00:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C19443861001 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712757656; bh=ffNiKGyc5DKTcAJEQlJj0kUwA7y/Mqvj42u7PhryOio=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JwH2eqKQzTomcVFEIr7ZYk13PboPq9d165llhswgvwzTbnaSdKAIYmeG/mX5MjiN4 aiA6Kngjwp5iIXmjSJuOJ6oI8fPD6KtUL2+pPG8cpZB2Ak67tgo7USnV1PQIczVjGE K7ZtsCu3MpRFNpIlslPx9//vxD4KMNVYR92SWst4= From: "acoplan at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/114674] [aarch64] ldp_fusion fails to merge 2 strs due to imprecise alignment info Date: Wed, 10 Apr 2024 14:00:56 +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: 14.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: acoplan at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: acoplan at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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=3D114674 Alex Coplan changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |acoplan at gcc dot = gnu.org Status|NEW |ASSIGNED --- Comment #4 from Alex Coplan --- Discussing offline with Richard S an alternative approach would be to use replace_equiv_address[_nv] instead of adjust_address[_nv]; that way we pres= erve most properties of the original mem and just take the address from the othe= r. In fact this is what aarch64_check_consecutive_mems already does so I think= we should follow that. I'll try a patch along those lines for stage 1.=