public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug debug/70764] FAIL: gcc.dg/guality/pr41447-1.c fails on aarch64
[not found] <bug-70764-4@http.gcc.gnu.org/bugzilla/>
@ 2021-08-31 5:52 ` pinskia at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: pinskia at gcc dot gnu.org @ 2021-08-31 5:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70764
Andrew Pinski <pinskia at gcc dot gnu.org> 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=none |
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to ktkachov from comment #0)
> Note that this test was already failing for other optimisation levels before
> that change:
>
> 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
>
> That patch controlled the way -fomit-frame-pointer is turned on, which
> probably affected debug info generation, so it is very likely that the patch
> 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-08-31 5:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-70764-4@http.gcc.gnu.org/bugzilla/>
2021-08-31 5:52 ` [Bug debug/70764] FAIL: gcc.dg/guality/pr41447-1.c fails on aarch64 pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).