[PATCH][fortran] Rework allocator library interface
Jack Howarth
howarth@bromo.msbb.uc.edu
Tue Dec 12 19:13:00 GMT 2006
No problems here with a bootstrap of the current gcc trunk
and the proposed patch on i686-pc-linux-gnu. I get the following
results with a build on Fedora Core 6...
Native configuration is i686-pc-linux-gnu
=== gfortran tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/howarth/src/gcc-4.3-20061212/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/howarth/src/gcc-4.3-20061212/gcc/testsuite/gfortran.dg/dg.exp ...
Running /home/howarth/src/gcc-4.3-20061212/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
Running /home/howarth/src/gcc-4.3-20061212/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running /home/howarth/src/gcc-4.3-20061212/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp ...
Running /home/howarth/src/gcc-4.3-20061212/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp ...
=== gfortran Summary ===
# of expected passes 15626
# of expected failures 7
# of unsupported tests 16
/home/howarth/src/linux_obj/gcc/testsuite/gfortran/../../gfortran version 4.3.0 20061212 (experimental)
Perhaps you should try a clean svn pull or at least run 'svn diff' to make sure
you don't have additional changes in your gcc source tree.
Jack
On Mon, Dec 11, 2006 at 09:42:34PM +0100, Thomas Koenig wrote:
> On Mon, Dec 11, 2006 at 06:14:56PM +0100, Richard Guenther wrote:
>
> > Bootstrapped and tested on x86_64-unknown-linux-gnu.
> >
> > Ok for mainline? (4.2?)
>
> Regression-test fails for me on i686-pc-linux-gnu:
>
> Running /home/ig25/gcc/trunk/gcc/testsuite/gfortran.dg/dg.exp ...
> FAIL: gfortran.dg/allocatable_function_1.f90 -O0 scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -O1 scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -O2 scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -O3 -fomit-frame-pointer scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -O3 -fomit-frame-pointer -funroll-loops scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -O3 -g scan-tree-dump-times free 10
> FAIL: gfortran.dg/allocatable_function_1.f90 -Os scan-tree-dump-times free 10
>
> This is probably due to too new alias information making some calls
> to free redundant.
>
> FAIL: gfortran.dg/array_section_1.f90 -O0 execution test
> FAIL: gfortran.dg/array_section_1.f90 -O1 execution test
> FAIL: gfortran.dg/array_section_1.f90 -O2 execution test
> FAIL: gfortran.dg/array_section_1.f90 -O3 -fomit-frame-pointer execution test
> FAIL: gfortran.dg/array_section_1.f90 -O3 -fomit-frame-pointer -funroll-loops execution test
> FAIL: gfortran.dg/array_section_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test
> FAIL: gfortran.dg/array_section_1.f90 -O3 -g execution test
> FAIL: gfortran.dg/array_section_1.f90 -Os execution test
>
> A problem with a function with side effects here.
>
> Thomas
More information about the Fortran
mailing list