From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 13B34383E838; Tue, 9 Jun 2020 13:38:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 13B34383E838 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591709926; bh=H+a2yCUAt4CNazzXpCB31C5dBwznwqEhD/vrIlzoLtM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gyzlhxz7mmIAb+NNW4laL1aLvnHxDKubRjNBrule7XvV7Ncg6cjtjwkEYD8xxXV9Y P2NObtT1F9VBYlJHV8kMA7fj4uc6+P+fDRAIdAcc8kv6E4s8sKqH09MJ6cBJReVrls nd7BIxpISbHj9OH6ipW4n1ZEtHDch2Zl9cCNOIa8= From: "gcc at pkh dot me" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/95189] [10/11 Regression] memcmp being wrongly stripped like strcmp Date: Tue, 09 Jun 2020 13:38:45 +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: 10.1.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: gcc at pkh dot me X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.2 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, 09 Jun 2020 13:38:46 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95189 --- Comment #5 from gcc at pkh dot me --- I'd like to point out that this regression impacts badly a production app. We're using this pattern to compare an input vector of floats to a vector of zeros, but the comparison always returns 0 now, which basically breaks everything. We do have a workaround (removing the "=3D {0}"), but I don't t= hink this is an isolate case. Maybe the priority could be raised?=