Package: atlas Version: 3.8.3-29 Severity: serious When building an *unmodified* atlas source on sid/amd64, I see command lines like the following:
gcc -o ATL_xerbla.o -c -DL2SIZE=4194304 -I/tmp/atlas-3.8.3/build/atlas-base/include -I/tmp/atlas-3.8.3/build/atlas-base/../..//include -I/tmp/atlas-3.8.3/build/atlas-base/../..//include/contrib -DAdd_ -DF77_INTEGER=int -DStringSunStyle -DATL_OS_Linux -DATL_ARCH_Core2 -DATL_CPUMHZ=2000 -DATL_USE64BITS -DATL_GAS_x8664 -DWALL -DATL_NCPU=2 -fomit-frame-pointer -mfpmath=sse -msse3 -O2 -Wa,--noexecstack -fPIC -m64 /tmp/atlas-3.8.3/build/atlas-base/../..//src/auxil/ATL_xerbla.c The problem here is -msse3. Not all amd64 machines support SSE3 (in /proc/cpuinfo, pni), although mine does. A package built this way will almost certainly fail on systems that do not. Also, -DATL_ARCH_Core2 makes me nervous as well; if that enables anything that the lowest common denominator amd64 machine would not have, it will break things. And again, atlas should not need to know how fast my CPU is (-DATL_CPUMHZ); that also isn't portable. Optimization flags on amd64 should really be limited in this case to -O2 -fomit-frame-pointer. -mfpmath=sse is the default on amd64, and so is -m64. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
