From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 141633861032; Wed, 29 Jul 2020 07:56:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 141633861032 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1596009378; bh=0+ExFbrRD2UFaKuNm8k15wpCMKpDpfEXGltYCTp0Lzs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TdXUwR1jH83uzuX4+YzsaVbS3Z3/ktfSXRCb8GmXh+N6faP4OSvdOW7K2GwQFpTff H8z2hMI5pfw7oKFkkRZchK42RJ/nAQ5UV4gFjvj/sPQKS6YPVvPiMik/oFSm4C5f6N 1bPMQmFr1lQOBUOvyAGvPEZU1VDgU4mM4G5UamzI= From: "aros at gmx dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/96337] [10/11 Regression] GCC 10.2: twice as slow for -O2 -march=x86-64 vs. GCC 9.3/8.4 Date: Wed, 29 Jul 2020 07:56:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 10.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: aros at gmx 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: 10.3 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: Wed, 29 Jul 2020 07:56:18 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96337 --- Comment #12 from Artem S. Tashkinov --- Michael has admitted that might be a specific CPU relate regression: > Been running some more tests today: > - Tried on a i9-10980XE Cascade Lake and Cascade Lake Xeon systems and di= d not reproduce... > - I went back to the i9-10900K and picked just a few of the tests where i= t was impacted the hardest, but then surprisingly the results were similar = that run. Source: https://www.phoronix.com/forums/forum/software/programming-compilers/119678= 9-gcc-benchmarks-at-varying-optimization-levels-with-core-i9-10900k-show-an= -unexpected-surprise?p=3D1197196#post1197196 The plot thickens.=