This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/82005] [8 regression] early lto debug creates invalid assembly on Darwin
- From: "dominiq at lps dot ens.fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 28 Feb 2018 16:31:35 +0000
- Subject: [Bug target/82005] [8 regression] early lto debug creates invalid assembly on Darwin
- Auto-submitted: auto-generated
- References: <bug-82005-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82005
--- Comment #30 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> However I have restore my testing of the gfortran test suite with -g -flto
> and I see the following new failures:
>
> FAIL: gfortran.dg/namelist_14.f90 -g -flto (internal compiler error)
> FAIL: gfortran.dg/namelist_14.f90 -g -flto (test for excess errors)
> FAIL: gfortran.dg/namelist_69.f90 -g -flto (internal compiler error)
> FAIL: gfortran.dg/namelist_69.f90 -g -flto (test for excess errors)
> FAIL: gfortran.dg/namelist_70.f90 -g -flto (internal compiler error)
> FAIL: gfortran.dg/namelist_70.f90 -g -flto (test for excess errors)
This is caused by revision r251448 and "fixed" by restoring the gcc_assert in
r251447.
I also see
FAIL: libgomp.fortran/taskloop3.f90 -g -flto (internal compiler error)
which appeared between r251187 and r251447.
IMO the patch in comment 26 should be committed.