Merge pull request #274 from insertinterestingnamehere/drop_compilers

Drop Support for Old/Broken Compilers

Author: insertinterestingnamehere

README.md

@@ -134,38 +134,4 @@ For example, `Collect<mt_loop_traits::Add>` is rougly equivalent to the followin
     retval += function(args);
   }
 ```
-******************************************************
-
-##NOTE FOR PGI USERS
-pgcc needs the `-c9x` flag in order to correctly process variadic macros (which
-are used in qthread.c) and the PRIuMAX format definitions (used in `qalloc.c`).
-Use the CFLAGS variable to add this flag. Note that pgcc's support for the full
-C90/C99 standards is lousy, so most C90/C99 features that COULD be used are
-avoided.
-
-******************************************************
-
-##NOTE FOR IBM XL USERS
-make check will probably fail with the error:
-
-`xlc++: 1501-210 command option t contains an incorrect subargument`
-`.../.libs/libqthread.so: could not read symbols: Invalid operation`
-
-This does not mean that the library did not compile correctly, but instead
-means that your libtool is probably broken (most are). The problem seems to be
-that the wrapper script (testloop) is created with incorrect arguments to
-xlc++. The other wrapper scripts (e.g. test1/test2/test3/testq) all have the
-correct arguments, and if you modify testloop so that $relink_command uses the
-`-Wl,--rpath -Wl,directory` syntax rather than the `-rpath,directory` syntax,
-it would work just fine.
-
-*******************************************************
-
-## NOTE FOR IBM BLUEGENE/P GCC USERS
-Old versions of GCC do not handle builtin atomics correctly on this platform.
-The non-existence of `__sync_fetch_and_add()` cannot be reliably detected, so to
-use those compilers, you probably need to configure with
-`--disable-internal-spinlock`.
-
-*******************************************************
 

config/ax_c_restrict.m4

@@ -68,8 +68,6 @@
 # the same family, and in the presence of varying compiler options.  If only
 # plain "restrict" works, do nothing.  Here are some variants:
 # - GCC supports both __restrict and __restrict__
-# - older DEC Alpha C compilers support only __restrict
-# - _Restrict is the only spelling accepted by Sun WorkShop 6 update 2 C
 # Otherwise, define "restrict" to be empty.
 AN_IDENTIFIER([restrict], [AX_C_RESTRICT])
 AC_DEFUN([AX_C_RESTRICT],
@@ -95,15 +93,7 @@ AC_DEFUN([AX_C_RESTRICT],
    nothing if this is not supported.  Do not define if restrict is
    supported directly.  */
 #undef restrict
-/* Work around a bug in Sun C++: it does not support _Restrict or
-   __restrict__, even though the corresponding Sun C compiler ends up with
-   "#define restrict _Restrict" or "#define restrict __restrict__" in the
-   previous line.  Perhaps some future version of Sun C++ will work with
-   restrict; if so, hopefully it defines __RESTRICT like Sun C does.  */
-#if defined __SUNPRO_CC && !defined __RESTRICT
-# define _Restrict
-# define __restrict__
-#endif])
+])
  case $ac_cv_c_restrict in
    restrict) ;;
    no) AC_DEFINE([restrict], []) ;;

config/ax_openmp.m4

@@ -72,9 +72,9 @@ AC_PREREQ(2.59) dnl for _AC_LANG_PREFIX
 
 AC_CACHE_CHECK([for OpenMP flag of _AC_LANG compiler], ax_cv_[]_AC_LANG_ABBREV[]_openmp, [save[]_AC_LANG_PREFIX[]FLAGS=$[]_AC_LANG_PREFIX[]FLAGS
 ax_cv_[]_AC_LANG_ABBREV[]_openmp=unknown
-# Flags to try:  -fopenmp (gcc), -openmp (icc), -mp (SGI & PGI),
-#                -xopenmp (Sun), -omp (Tru64), -qsmp=omp (AIX), none
-ax_openmp_flags="-fopenmp -openmp -mp -xopenmp -omp -qsmp=omp none"
+# Flags to try:  -fopenmp (gcc), -openmp (icc), -mp (SGI),
+#                -omp (Tru64), -qsmp=omp (AIX), none
+ax_openmp_flags="-fopenmp -openmp -mp -omp -qsmp=omp none"
 if test "x$OPENMP_[]_AC_LANG_PREFIX[]FLAGS" != x; then
   ax_openmp_flags="$OPENMP_[]_AC_LANG_PREFIX[]FLAGS $ax_openmp_flags"
 fi

config/qthread_check_assembly.m4

@@ -78,68 +78,6 @@ rm -rf conftest*
 unset qthread_assemble
 ])dnl
 
-
-dnl #################################################################
-dnl
-dnl QTHREAD_CHECK_INLINE_GCC
-dnl
-dnl Check if the compiler is capable of doing GCC-style inline
-dnl assembly.  Some compilers emit a warning and ignore the inline
-dnl assembly (xlc on OS X) and compile without error.  Therefore,
-dnl the test attempts to run the emited code to check that the
-dnl assembly is actually run.  To run this test, one argument to
-dnl the macro must be an assembly instruction in gcc format to move 
-dnl the value 0 into the register containing the variable ret.  
-dnl For PowerPC, this would be:
-dnl
-dnl   "li %0,0" : "=&r"(ret)
-dnl
-dnl DEFINE QTHREAD_GCC_INLINE_ASSEMBLY to 0 or 1 depending on GCC
-dnl                support
-dnl
-dnl #################################################################
-AC_DEFUN([QTHREAD_CHECK_INLINE_C_GCC],[
-  AC_CACHE_CHECK([support for __asm__ __volatile__],
-	             [qt_cv_asm_volatile],
-				 [AC_LINK_IFELSE([AC_LANG_PROGRAM([[]],[[__asm__ __volatile__ ("":::"memory");]])],
-					             [qt_cv_asm_volatile=yes],
-								 [qt_cv_asm_volatile=no])])
-  AC_CACHE_CHECK([$CC support for GCC inline assembly],[qt_cv_gcc_inline_assembly],[
-  assembly="$1"
-  asm_result="unknown"
-  AS_IF([test ! "$assembly" = ""],
-        [AC_RUN_IFELSE([AC_LANG_SOURCE([[
-int main(void) {
-int ret = 1;
-__asm__ __volatile__ ($assembly);
-return ret;
-}]])],
-      [asm_result="yes"], [asm_result="no"], 
-      [asm_result="unknown"])],
-	    [assembly="test skipped - assuming no"])
-
-  # if we're cross compiling, just try to compile and figure good enough
-  AS_IF([test "$asm_result" = "unknown"],
-    [AC_LINK_IFELSE([AC_LANG_SOURCE([[
-int main(void)
-{
-int ret = 1;
-__asm__ __volatile__ ($assembly);
-return ret;
-}]])],
-      [asm_result="yes"], [asm_result="no"])
-  ])
-  qt_cv_gcc_inline_assembly="$asm_result"
-  unset assembly asm_result])
-
-
-  AS_IF([test "x$qt_cv_gcc_inline_assembly" = "xyes"],
-    [AC_DEFINE([HAVE_GCC_INLINE_ASSEMBLY], [1],
-       [Whether C compiler supports GCC style inline assembly])
-     $2], [$3])
-])dnl
-
-
 AC_DEFUN([QTHREAD_CHECK_ASSEMBLY],[
   AC_REQUIRE([AM_PROG_AS])
   AC_CHECK_SIZEOF([long])
@@ -190,9 +128,6 @@ AC_DEFUN([QTHREAD_CHECK_ASSEMBLY],[
 
   esac
 
-  # now that we know our architecture, try to inline assemble
-  QTHREAD_CHECK_INLINE_C_GCC([$qthread_gcc_inline_assign], [$1], [$2])
-
   AC_MSG_CHECKING([for asssembly architecture])
   AC_MSG_RESULT([$qthread_cv_asm_arch])
   result="QTHREAD_$qthread_cv_asm_arch"

config/qthread_check_atomics.m4

@@ -10,11 +10,6 @@ AC_REQUIRE([QTHREAD_DETECT_COMPILER_TYPE])
 AC_ARG_ENABLE([builtin-atomics],
      [AS_HELP_STRING([--disable-builtin-atomics],
 	                 [force the use of inline-assembly (if possible) rather than compiler-builtins for atomics. This is useful for working around some compiler bugs; normally, it's preferable to use compiler builtins.])])
-AS_IF([test "x$enable_builtin_atomics" != xno],
-      [AS_IF([test "x$qthread_cv_c_compiler_type" = xIBM_XL -o "x$qthread_cv_cxx_compiler_type" = xIBM_XL],
-		     [AS_IF([test "x$enable_builtin_atomics" = xyes],
-				    [AC_MSG_WARN([Disabling builtin atomics on IBM_XL, due to compiler design decision])])
-			  enable_builtin_atomics=no])])
 AC_CACHE_CHECK([whether compiler supports builtin atomic CAS-32],
   [qthread_cv_atomic_CAS32],
   [AC_LINK_IFELSE([AC_LANG_SOURCE([[

config/qthread_check_attributes.m4

@@ -100,14 +100,12 @@ AC_DEFUN([QTHREAD_BUILTIN_PREFETCH],[dnl
 AC_CACHE_CHECK(
  [support for __builtin_prefetch],
  [qt_cv_builtin_prefetch],
- [AS_IF([test "$qthread_cv_c_compiler_type" == PortlandGroup],
-        [qt_cv_builtin_prefetch=no],
-		[AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include <stdlib.h>
+ [AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include <stdlib.h>
 int x;]],[[
 __builtin_prefetch(&x, 0, 0);
 return malloc(x)?1:0;]])],
  [qt_cv_builtin_prefetch=yes],
- [qt_cv_builtin_prefetch=no])])])
+ [qt_cv_builtin_prefetch=no])])
  AS_IF([test "x$qt_cv_builtin_prefetch" = xyes],
  	   [AC_DEFINE([HAS_BUILTIN_PREFETCH], [1], [define if compiler supports __builtin_prefetch])
 	   $1], [$2])