From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 11DE13858C54; Mon, 5 Feb 2024 07:35:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 11DE13858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707118559; bh=Wv7WAphj7eNsb5uji49NBX8BLHmvzdQFNg951gskemE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hUTtuK62qBm6Fgw5LN7EBpHENAUc0ipky9CzH4P4z5116hhjraaXTq1xcZPX4oZiT Sq1HRZNkUviKg4ajC0jUoV6vhqHHnDHLLbkjPrkH9BIt1lbjQ5YaS+G42Hfwd1A+gt B862oo0EKrX6Zu1x6B8t/3wPw/3gaKSFxd7bJQ6A= From: "cvs-commit at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113255] [11/12/13 Regression] wrong code with -O2 -mtune=k8 Date: Mon, 05 Feb 2024 07:35:55 +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: 13.2.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.5 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://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113255 --- Comment #17 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:5b281946c4b51132caf5e5b64c730fef92dd6123 commit r14-8796-g5b281946c4b51132caf5e5b64c730fef92dd6123 Author: Richard Biener Date: Thu Feb 1 13:54:11 2024 +0100 target/113255 - avoid REG_POINTER on a pointer difference The following avoids re-using a register holding a pointer (and thus might be REG_POINTER) for the result of a pointer difference computation. That might confuse heuristics in (broken) RTL alias analysis which relies on REG_POINTER indicating that we're dealing with one. This alone doesn't fix anything. PR target/113255 * config/i386/i386-expand.cc (expand_set_or_cpymem_prologue_epilogue_by_misaligned_moves): Use a new pseudo for the skipped number of bytes.=