summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJames Laird <jlaird@hdfgroup.org>2006-03-24 20:28:01 (GMT)
committerJames Laird <jlaird@hdfgroup.org>2006-03-24 20:28:01 (GMT)
commitd88d363ef9f37977724853a967ff7b7b9005671a (patch)
treed349e3bad11765845b0cc9e187707dcfd196630a
parentef9835e89dd7a9a39dcf53155e47593a97651ac7 (diff)
downloadhdf5-d88d363ef9f37977724853a967ff7b7b9005671a.zip
hdf5-d88d363ef9f37977724853a967ff7b7b9005671a.tar.gz
hdf5-d88d363ef9f37977724853a967ff7b7b9005671a.tar.bz2
[svn-r12154] Purpose:
Removed -march flag Description: The -march optimization flag is bad in some circumstances Solution: Prevented HDF5 from adding the -march archicture-specific optimization flag, so that users could have one version of HDF5 used by several different machines. Platforms tested: heping (one of the few platforms that affected by this small change)
-rw-r--r--config/gnu-flags10
1 files changed, 8 insertions, 2 deletions
diff --git a/config/gnu-flags b/config/gnu-flags
index f081e55..84b7196 100644
--- a/config/gnu-flags
+++ b/config/gnu-flags
@@ -117,13 +117,19 @@ case "$cc_vendor-$cc_version" in
case "$host_cpu_model" in
# Hmm.. this might not catch Celerons, but it won't hurt them either...
*Pro*|*II*|*III*|*IV*|*Athlon*)
- arch="-march=i686"
+ # architecture-specific optimizations cause problems
+ # for some users who build binaries to be used on
+ # multiple architectures.
+ # arch="-march=i686"
;;
esac
;;
*-i686)
- arch="-march=i686"
+ # architecture-specific optimizations cause problems
+ # for some users who build binaries to be used on
+ # multiple architectures.
+ # arch="-march=i686"
;;
esac