From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D0D853858D35; Thu, 30 Jul 2020 19:52:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D0D853858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1596138750; bh=mLCEqMkF9uVJoEnvh5WYgO/cvF2D9f79eq9f2L6jOB8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hrFx/LDSbZ8Ob3rcsFLzy4b54p8/+jwurn8PQhI6NZfUGYtWOptxtl2/aLE5zF0t8 J/huSeDq0Sy1lc3Aafi7ayp/Qyhs7w8+8DMaOry6b5v2tGUFCqFBn94ra4PvWL+zjU HWuX+a9rzS9ITD1mTUg8/Q79DKa/wh8P8pNZUUv8= From: "jamborm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/84490] [8/9/10/11 regression] 436.cactusADM regressed by 6-8% percent with -Ofast on Zen and Haswell, compared to gcc 7.2 Date: Thu, 30 Jul 2020 19:52:30 +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: 8.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 8.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 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: Thu, 30 Jul 2020 19:52:30 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D84490 --- Comment #15 from Martin Jambor --- The problem sometimes is still there, sometimes it isn't: https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=3D37.100.0&plot.1= =3D27.100.0& I wonder whether we should keep this bug opened, the benchmark seems too erratic.=