From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A6C9C3858C3A; Mon, 12 Feb 2024 12:57:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A6C9C3858C3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707742651; bh=wcxQyrsFYNynoxlM8tN9G6bTlBUjoPlaGWy4P4WuoDc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=c/MsmaJPV442q/LtpNNxG+3Tn65O3hA7BAnu844e/113Mzyh/NeACqayDVN8tueM4 eqRzhwZUJQ9R6zzFZ7kt/zoWlSRZE32GOlwwXoe/M0zlCC6/1t07AgHejbcA9cd78M f1NnOjG6ufURw2Q1yNxgTCAR/YcESKWevEtIpUmc= From: "jamborm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113833] 435.gromacs fails verification on with -Ofast -march={cascadelake,icelake-server} and PGO after r14-7272-g57f611604e8bab Date: Mon, 12 Feb 2024 12:57:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm at gcc dot gnu.org 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: attachments.created 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=3D113833 --- Comment #4 from Martin Jambor --- Created attachment 57397 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D57397&action=3Dedit -fopt-info-vec before/after comparison (In reply to Richard Biener from comment #3) > A compare before/after the patch of -fopt-info-vec output might show the = few > cases that are affected by the patch. I Hope I have not messed anything up. I have added -fopt-info-vec right af= ter -fprofile-use into the spec config and then grepped the output for ':[^:]*:[^:]*: optimized'. Then I sorted (because the build was parallel) = and compared the output and it seems there are quite a few *fewer* instances of vectorization happening.=