From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 801313857030; Sat, 1 Aug 2020 18:53:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 801313857030 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1596307994; bh=YoSqUYEAQFXnuCAAS3zW/GcC68k3uiGGG+VJuzSlH+c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nvSHoj6fTbJp9ouBtM3d7iaeSTutK+GN1HZRGgM4RoHGgYamTL+cQIlcpArxxAMdZ zaEQZKSyBX3pMnSiTYrPdYfkWuT17PQUkj4eJWMCBbUk6AOihgR+8EjRz/WuoDWPWt lmQjsfs40f8ZcYPSPnfb+OCX3gGjvWsG9H16bC+8= From: "andysem at mail dot ru" 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: Sat, 01 Aug 2020 18:53:14 +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: andysem at mail dot ru 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: Sat, 01 Aug 2020 18:53:14 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96337 --- Comment #13 from andysem at mail dot ru --- I think, this inliner change needs to be reverted. People expect -O2 to pro= duce decently optimized binaries, and starting with gcc 10.x it doesn't deliver.= -O3 traditionally enabled optimizations that may or may not improve performance (and historically, sometimes even break code), so most projects don't use i= t. If there needs to be an optimization mode that prioritizes compilation speed then let that be a separate mode, e.g. -O1.=