Re: [autovect] [patch] branch merge

[Sebastian Pop <sebastian dot pop at cri dot ensmp dot fr>]

Thanks for this huge merge from mainline.  I've bootstrapped
autovect-branch on i686.  Testing shows no regressions other than
those reported, with the exception of:

gfortran.dg/pr17706.f90 which is passing on i686,

FAIL: gcc.dg/tree-ssa/20041110-1.c (test for excess errors)
FAIL: gcc.dg/tree-ssa/pr17100.c scan-tree-dump-times Replacing one of the conditions 1

FAIL: gcc.dg/vect/vect-reduc-1.c execution test
FAIL: gcc.dg/vect/vect-reduc-1char.c execution test
FAIL: gcc.dg/vect/vect-reduc-1short.c execution test
FAIL: gcc.dg/vect/vect-reduc-2.c execution test
FAIL: gcc.dg/vect/vect-reduc-2char.c execution test
FAIL: gcc.dg/vect/vect-reduc-2short.c execution test
FAIL: gcc.dg/vect/vect-reduc-3.c execution test
FAIL: gcc.dg/vect/vect-reduc-7.c execution test
FAIL: gcc.dg/vect/vect-reduc-8.c execution test
FAIL: gcc.dg/vect/vect-reduc-9.c execution test
FAIL: gcc.dg/vect/fast-math-vect-reduc-5.c execution test
FAIL: gcc.dg/vect/fast-math-vect-reduc-7.c (test for excess errors)
WARNING: gcc.dg/vect/fast-math-vect-reduc-7.c compilation failed to produce executable
FAIL: gcc.dg/vect/fast-math-vect-reduc-7.c scan-tree-dump-times vectorized 3 loops 1

I can provide detailed info for each fail if needed.

Dorit Naishlos wrote:
> 
> Remaining issues:
> - scev_const_prop bootstrap failure

I've given a look at this one:

(gdb) p type
$1 = 0x0
(gdb) p name
$2 = 0x2aaaab735620
(gdb) pgs
vec_D.28995_894

(gdb) pt
 <ssa_name 0x2aaaab735620 nothrow var <var_decl 0x2aaaab7dac60 vec_> def_stmt <ssa_name 0x2aaaabafe1c0>
    version 894 in-free-list>
(gdb) p phi
$4 = 0x2aaaab682900
(gdb) pgs
vec_D.28995_894 = PHI <0B(53), 0B(47)>;

(gdb) 

Seems like the type of a variable from vect_create_destination_var is
not correctly initialized?

Sebastian