Fixed autoconf tests for gfortran 4.0 and eliminated testing codes it…

… can't handle (when using gfortran 4.0).

git-svn-id: file:https:///usr/casc/overture/ROSE/svn/ROSE/trunk/ROSE@7428 a27c51de-2d2b-4d1b-a6e8-f7f87814f453

config/choose-backend-compiler.m4

@@ -102,8 +102,9 @@ dnl build using ROSE)
 
 # DQ (9/16/2009): GNU gfortran 4.0 has special problems so we avoid some tests where it fails.
  gfortran_version_4_0=no
- if test x$BACKEND_FORTRAN_COMPILER_MAJOR_VERSION_NUMBER == x; then
- if test x$BACKEND_FORTRAN_COMPILER_MINOR_VERSION_NUMBER == x; then
+ if test x$BACKEND_FORTRAN_COMPILER_MAJOR_VERSION_NUMBER == x4; then
+ if test x$BACKEND_FORTRAN_COMPILER_MINOR_VERSION_NUMBER == x0; then
+ echo "Note: we have identified version 4.0 of gfortran!"
  gfortran_version_4_0=yes
  fi
  fi
@@ -113,6 +114,7 @@ dnl build using ROSE)
  gfortran_version_4_1=no
  if test x$BACKEND_FORTRAN_COMPILER_MAJOR_VERSION_NUMBER == x4; then
  if test x$BACKEND_FORTRAN_COMPILER_MINOR_VERSION_NUMBER == x1; then
+ echo "Note: we have identified version 4.1 of gfortran!"
  gfortran_version_4_1=yes
  fi
  fi

docs/Rose/FAQ.tex

@@ -364,6 +364,31 @@ \chapter{ FAQ }
 
 \end{enumerate}
 
+\commentout{
+
+* Question from Antoine Colin (9/19/2009):
+I recently found the ROSE compiler infrastructure and it looks very attractive for my work (building a prototype C++ instrumenter).
+The documentation mentions port on cygwin in a few places, but the download links do not seem to point at any?
+Is there a version available that can be compiled/linked on cygwin?
+
+Answer from Dan:
+ We have internally compiled ROSE on cygwin, and while it
+works, we don't try to release a cygwin binary of the EDG work that
+would be required for an external release. So we don't really officially
+support it. I find Cygwin to be so slow that working with ROSE on cygwin
+is (I think) a painful process. So I'm not really supportive of a making cygwin
+an official supported platform for ROSE. I suggest you use a linux or Mac OSX
+platform, you will be much happier with the resulting working environment.
+
+
+
+* Question about ROSE License policy (submitted to rose-public mailing list week of 9/14/09)
+
+
+
+}
+
+
 \commentout{
 Tool Demos at Dagstuhl: Scalable Program Analysis
 

tests/CompileTests/Fortran_tests/Makefile.am

@@ -135,6 +135,7 @@ F90_TESTCODES_REQUIRED_TO_PASS = \
  canonicalExample.f90 
 
 if !ROSE_USING_GFORTRAN_VERSION_4_0
+ # These are tests that fail using the gfrotran version 4.0 compiler (but pass with all other versions of gfortran).
  F90_TESTCODES_REQUIRED_TO_PASS += test2007_263.f90
 endif
 

tests/CompileTests/OpenMP_tests/fortran/Makefile.am

@@ -13,11 +13,15 @@ F77_TESTCODES_TO_PASS = \
 
 F90_TESTCODES_TO_PASS = \
  paralledo.f90 \
- exampleA134f.f90 \
  collapse.f90 \
  critical.f90 \
  continuation.f90
 
+if !ROSE_USING_GFORTRAN_VERSION_4_0
+ # These are tests that fail using the gfrotran version 4.0 compiler (but pass with all other versions of gfortran).
+ F90_TESTCODES_TO_PASS += exampleA134f.f90
+endif
+
 # see bug 350, wrong position for C$OMP END PARALLEL
 # case insensitive in symobl lookup for Fortran
 # exampleA281f.f: case insensitive for included header file's name, also bug 354