From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B6DC43895FE6; Thu, 24 Nov 2022 23:22:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B6DC43895FE6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669332172; bh=YsVc0jUliywlJdhccvg2aH8Xt/Gr7x925DmXw19wseo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GhMF0tAOynbprDoHmKJsSHMZVG6LkGaVfL/R3aVYJ+047mfbAKppt/kusGwFYv3s5 JThYrfLqWly5tks2LK4A7bSH1F2LsxZ2VHYZcSaHIsbmxfYSjpIGZurq725QBUsT6p mGfIoP2hl4TI+xVS1CcNKvDxNL1pKo/KOe6QEaBY= From: "already5chosen at yahoo dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97832] AoSoA complex caxpy-like loops: AVX2+FMA -Ofast 7 times slower than -O3 Date: Thu, 24 Nov 2022 23:22:50 +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: 10.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: already5chosen at yahoo dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 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=3D97832 --- Comment #14 from Michael_S --- I tested a smaller test bench from Comment 3 with gcc trunk on godbolt. Issue appears to be only partially fixed. -Ofast result is no longer a horror that it was before, but it is still not= as good as -O3 or -O2. -Ofast code generation is still strange and there are f= ew vblendpd instruction that serve no useful purpose. And -O2/O3 is still not as good as it should be or as good as icc. But, as mentioned in my original post, over-aggressive load+op combining is= a separate problem.=