https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66280

Salvatore Filippone <sfilippone at uniroma2 dot it> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sfilippone at uniroma2 dot it

--- Comment #11 from Salvatore Filippone <sfilippone at uniroma2 dot it> ---
(In reply to Richard Biener from comment #9)
> Fixed on trunk sofar.

I still see this (or a very similar) error from the Fortran front-end at
r224364:

[sfilippo@epsilon NewPSBLAS]$ gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/opt/gnu/6.0.0/libexec/gcc/x86_64-unknown-linux-gnu/6.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc/configure --prefix=/opt/gnu/6.0.0
--enable-languages=c,c++,fortran --with-gmp=/usr/local/travel/GNU/gmp
--with-mpfr=/usr/local/travel/GNU/mpfr --with-mpc=/usr/local/travel/GNU/mpc
--with-isl=/usr/local/travel/GNU/isl
Thread model: posix
gcc version 6.0.0 20150611 (experimental) (GCC) 
[sfilippo@epsilon NewPSBLAS]$ gfortran -O3 -c mv.f90
mv.f90:1:0:

 subroutine mv(m,n,nc,alpha,irp,ja,val,&
^
internal compiler error: in vect_get_vec_def_for_operand, at
tree-vect-stmts.c:1478
0xdbc689 vect_get_vec_def_for_operand(tree_node*, gimple_statement_base*,
tree_node**)
        ../../gcc/gcc/tree-vect-stmts.c:1478
0xdc4ebc vectorizable_store
        ../../gcc/gcc/tree-vect-stmts.c:5330
0xdcfba6 vect_transform_stmt(gimple_statement_base*, gimple_stmt_iterator*,
bool*, _slp_tree*, _slp_instance*)
        ../../gcc/gcc/tree-vect-stmts.c:7496
0xde90d5 vect_schedule_slp_instance
        ../../gcc/gcc/tree-vect-slp.c:3481
0xde96c6 vect_schedule_slp(_loop_vec_info*, _bb_vec_info*)
        ../../gcc/gcc/tree-vect-slp.c:3551
0xdd4bf7 vect_transform_loop(_loop_vec_info*)
        ../../gcc/gcc/tree-vect-loop.c:6218
0xdef242 vectorize_loops()
        ../../gcc/gcc/tree-vectorizer.c:495
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Salvatore

Reply via email to