This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917
- From: "aldyh at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 05 Feb 2018 14:47:26 +0000
- Subject: [Bug tree-optimization/82518] [8 regression] gfortran.fortran-torture/execute/in-pack.f90 fails on armeb since r252917
- Auto-submitted: auto-generated
- References: <bug-82518-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518
--- Comment #18 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #17)
> (In reply to Aldy Hernandez from comment #12)
>
> > along with the isub8 subroutine, and continue chopping things similarly
> > upward until you get to the abort that fails. Then see if you can chop
> > non-dependent things from the top down until you get to the smallest block
> > that has no problem before 197671 and a problem after 197815 (with -O3 -g
> > -fno-vect-cost-model as suggested before).
> >
> Hmmm does -O3 overrides -fno-vect-cost-model?
>
> When I running the testsuite with qemu/-fno-vect-cost-model (as target
> board), my logs show:
> [...]
> /home/christophe.lyon/src/GCC/sources/gcc-fsf/r197671/gcc/testsuite/gfortran.
> fortran-torture/execute/in-pack.f90 -fno-vect-cost-model
> -fno-diagnostics-show-caret -w -O3 -g [....]
>
> so I may not have been testing what I thought :(
-fno-vect-cost-model should take effect regardless of the -O3 specified. That
is, the order shouldn't matter.
BTW, I only mentioned -O3 -fno-vect-cost-model -g because that is what was
suggested by Jakub in comment #3.