On Mon, Oct 1, 2012 at 3:55 PM, Sharad Singhai <sing...@google.com> wrote:
> On Mon, Oct 1, 2012 at 6:52 AM, H.J. Lu <hjl.to...@gmail.com> wrote:
>> On Mon, Oct 1, 2012 at 6:49 AM, Sharad Singhai <sing...@google.com> wrote:
>>> I am sorry, I didn't enable all the languages. Will fix the fortran
>>> test breakage shortly.
>>
>> It is not just Fortran. There are some failures in C testcases.
>
> I checked and those files looked like generator files for Fortran
> tests and thus were not exercised in my configuration. I am really
> sorry about that. I am fixing it.
As I said, you should not enable/disable anything special but
configure with all default languages enabled (no --enable-languages)
and do toplevel make -k check, preferably also excercising
multilibs with RUNTESTFLAGS="--target_board=unix/\{,-m32\}"
Richard.
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11a.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11b.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11c.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-2.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-25.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-26.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-28.c
> UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-32.c
>
> Thanks,
> Sharad
>
>>
>>> Thanks,
>>> Sharad
>>> Sharad
>>>
>>>
>>> On Mon, Oct 1, 2012 at 4:50 AM, H.J. Lu <hjl.to...@gmail.com> wrote:
>>>> On Sun, Sep 30, 2012 at 11:36 PM, Sharad Singhai <sing...@google.com>
>>>> wrote:
>>>>> Resend to gcc-patches
>>>>>
>>>>> I have addressed the comments by fixing all the minor issues,
>>>>> bootstrapped and tested on x86_64. I did the recommended reshuffling
>>>>> by moving non-tree code from tree-dump.c into a new file dumpfile.c.
>>>>>
>>>>> I committed two successive revisions
>>>>> r191883 Main patch with the dump infrastructure changes. However, I
>>>>> accidentally left out a new file, dumpfile.c.
>>>>> r191884 Added dumpfile.c, and did the renaming of dump_* functions
>>>>> from gimple_pretty_print.[ch].
>>>>>
>>>>> As things stand right now, r191883 is broken because of the missing
>>>>> file 'dumpfile.c', which the very next commit fixes. Anyone who got
>>>>> broken revision r191883, please svn update. I am really very sorry
>>>>> about that.
>>>>>
>>>>> I have a couple more minor patches which deal with renaming; I plan to
>>>>> address those later.
>>>>>
>>>>
>>>> It caused:
>>>>
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11.c scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11a.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11a.c scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11b.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11b.c scan-tree-dump-times vect
>>>> "vectorized 0 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11c.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-11c.c scan-tree-dump-times vect
>>>> "vectorized 0 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-2.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-2.c scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-25.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-25.c scan-tree-dump-times vect
>>>> "vectorized 2 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-26.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect
>>>> "Alignment of access forced using peeling" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-28.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect
>>>> "Alignment of access forced using peeling" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-32.c (test for excess errors)
>>>> FAIL: gcc.dg/tree-ssa/gen-vect-32.c scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gfortran.dg/vect/O3-pr36119.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/O3-pr39595.f (test for excess errors)
>>>> FAIL: gfortran.dg/vect/Ofast-pr50414.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/cost-model-pr34445.f (test for excess errors)
>>>> FAIL: gfortran.dg/vect/cost-model-pr34445a.f (test for excess errors)
>>>> FAIL: gfortran.dg/vect/fast-math-pr38968.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/fast-math-pr38968.f90 scan-tree-dump vect
>>>> "vectorized 1 loops"
>>>> FAIL: gfortran.dg/vect/fast-math-real8-pr40801.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/fast-math-real8-pr40801.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/fast-math-vect-8.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/fast-math-vect-8.f90 scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gfortran.dg/vect/no-fre-no-copy-prop-O3-pr51704.f90 (test for
>>>> excess errors)
>>>> FAIL: gfortran.dg/vect/no-vfa-pr32377.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/no-vfa-pr32377.f90 scan-tree-dump-times vect
>>>> "vectorized 2 loops" 1
>>>> FAIL: gfortran.dg/vect/no-vfa-pr32457.f90 (test for excess errors)
>>>> FAIL: gfortran.dg/vect/no-vfa-pr32457.f90 scan-tree-dump-times vect
>>>> "vectorized 0 loops" 1
>>>> FAIL: gfortran.dg/vect/pr19049.f90 -O scan-tree-dump-times vect
>>>> "complicated access pattern" 1
>>>> FAIL: gfortran.dg/vect/pr19049.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr32377.f90 -O scan-tree-dump-times vect
>>>> "vectorized 2 loops" 1
>>>> FAIL: gfortran.dg/vect/pr32377.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr32380.f -O scan-tree-dump-times vect
>>>> "vectorized 6 loops" 1
>>>> FAIL: gfortran.dg/vect/pr32380.f -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr33301.f -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr50178.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr50412.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr51058-2.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr51058.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/pr51285.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/vect-1.f90 -O scan-tree-dump-times vect
>>>> "vectorized 3 loops" 1
>>>> FAIL: gfortran.dg/vect/vect-1.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/vect-2.f90 -O scan-tree-dump-times vect
>>>> "Alignment of access forced using peeling" 3
>>>> FAIL: gfortran.dg/vect/vect-2.f90 -O scan-tree-dump-times vect
>>>> "Vectorizing an unaligned access" 2
>>>> FAIL: gfortran.dg/vect/vect-2.f90 -O scan-tree-dump-times vect
>>>> "vectorized 3 loops" 1
>>>> FAIL: gfortran.dg/vect/vect-2.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/vect-3.f90 -O scan-tree-dump-times vect
>>>> "Alignment of access forced using peeling" 1
>>>> FAIL: gfortran.dg/vect/vect-3.f90 -O scan-tree-dump-times vect
>>>> "Vectorizing an unaligned access" 1
>>>> FAIL: gfortran.dg/vect/vect-3.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/vect-4.f90 -O scan-tree-dump-times vect
>>>> "Alignment of access forced using peeling" 1
>>>> FAIL: gfortran.dg/vect/vect-4.f90 -O scan-tree-dump-times vect
>>>> "Vectorizing an unaligned access" 1
>>>> FAIL: gfortran.dg/vect/vect-4.f90 -O scan-tree-dump-times vect
>>>> "accesses have the same alignment." 1
>>>> FAIL: gfortran.dg/vect/vect-4.f90 -O scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gfortran.dg/vect/vect-4.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/vect-5.f90 -O scan-tree-dump-times vect
>>>> "Alignment of access forced using peeling" 1
>>>> FAIL: gfortran.dg/vect/vect-5.f90 -O scan-tree-dump-times vect
>>>> "Vectorizing an unaligned access" 1
>>>> FAIL: gfortran.dg/vect/vect-5.f90 -O scan-tree-dump-times vect
>>>> "vectorized 1 loops" 1
>>>> FAIL: gfortran.dg/vect/vect-5.f90 -O (test for excess errors)
>>>> FAIL: gfortran.dg/vect/vect-6.f -O (test for excess errors)
>>>>
>>>> on Linux/x86.
>>>>
>>>> --
>>>> H.J.
>>
>>
>>
>> --
>> H.J.
