From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B8A473858401; Tue, 31 Aug 2021 05:52:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8A473858401 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/70764] FAIL: gcc.dg/guality/pr41447-1.c fails on aarch64 Date: Tue, 31 Aug 2021 05:52:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 5.3.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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: Tue, 31 Aug 2021 05:52:31 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D70764 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|PASS->FAIL: |FAIL: |gcc.dg/guality/pr41447-1.c |gcc.dg/guality/pr41447-1.c | -O2 -flto | fails on aarch64 |-fno-use-linker-plugin | |-flto-partition=3Dnone | --- Comment #4 from Andrew Pinski --- (In reply to ktkachov from comment #0) > Note that this test was already failing for other optimisation levels bef= ore > that change: >=20 > FAIL: gcc.dg/guality/pr41447-1.c -O2 execution test > FAIL: gcc.dg/guality/pr41447-1.c -O3 -g execution test > FAIL: gcc.dg/guality/pr41447-1.c -Os execution test >=20 > That patch controlled the way -fomit-frame-pointer is turned on, which > probably affected debug info generation, so it is very likely that the pa= tch > just triggered the same issue that caused the failure on the other > optimisation levels in this test. Right, in the case of -flto, the optimize attribute was being added to the functions so the testcase was actually just accidently passing before the patch. And since it was failing without -flto it is not a regression=