From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AE2423861015; Sat, 19 Sep 2020 21:49:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE2423861015 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1600552163; bh=SimADo6lvEB11ImwVnSRoHGnwe/Sf3ShRSRg8qUpUXo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kXuY73cDgCW2Vv9dWLwpoQQMnV/b/IZb1yvK6fuWMndt+x4kqH8dIkY04cpyYVmQA zjNkb2f2sCIH8sydZAjYeHahv7j+El4OyKRSdNU5KGOhMZ4nGllcKqWjMnXWlJcUTW 2ugDFpYSaqlE3GDnT+5PuGUykWIco3Pde6x3E5vI= From: "vz-gcc at zeitlins dot org" 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, 19 Sep 2020 21:49:23 +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: vz-gcc at zeitlins dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME 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, 19 Sep 2020 21:49:23 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96337 --- Comment #19 from Vadim Zeitlin --- (In reply to Jan Hubicka from comment #18) > We need a reproducer to fix bugs. Yes, of course, I understand this. I just didn't have time to make one yet, we've literally discovered the issue only today (well, maybe yesterday, depending on the time zone). > So if you have actual testcase that > slow down, it would be great to open separate bug report for that. OK, will do, but, at least superficially, our situation seems very similar = to this one, so I thought it would be better to keep this one going. But, agai= n, I'll open the new one as soon as I can make a test case for it, if this is = your preference.=