From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6DE3A385700D; Tue, 21 Jul 2020 22:13:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6DE3A385700D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595369630; bh=Ydp/kh2lDCZ0FBOWKwCPc7p0sW9C9PJncKcCqpc3JFU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RFPlgg9qcZacFsjpT9uo7YDerwd2UfDm/3w+/VabUZm+LibuCRlTTPoddLWqBuPU8 5zLHbI6DH4PDyULI3UBv3fqWDBacTBVxoduV1ClWk3j5aQASK5jQKUBBHfABVkHGRO Z1RRuwG5DH3+BXgIwQC5KZvItpMsZMchBDbDseoc= From: "gabravier at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96271] Failure to optimize memcmp of doubles to avoid going through memory Date: Tue, 21 Jul 2020 22:13:50 +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: 11.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: gabravier at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2020 22:13:50 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96271 --- Comment #2 from Gabriel Ravier --- What do you mean ? -march=3Dintel doesn't exist and I have tried -mtune=3Di= ntel, I see no difference in the handling of this regardless of any -march/tune fla= gs (I've tried : none, -march=3Dnocona, -march=3Dtigerlake, -mtune=3Dintel, -march=3Dznver2), unless there is somehow a big problem with `movq r64, xmm= ` on all x86-64 processors, this should be considered a bug.=