I wonder if it is a new intel compiler or if it never worked with that compiler. The latter seems unlikely though.
Bill. 2009/5/31 Jason Martin <[email protected]>: > > GMP-4.3 also fails to compiled with icc. The intel compiler doesn't > seem happy with the __asm__ syntax in the C files. > > Jason Worth Martin > Asst. Professor of Mathematics > http://www.math.jmu.edu/~martin > > > > On Sat, May 30, 2009 at 8:08 PM, Bill Hart <[email protected]> > wrote: >> >> This is unfortunate. Could you make a trac ticket for this and we'll >> try to fix this for the next release. >> >> Bill. >> >> 2009/5/31 Jason Moxham <[email protected]>: >>> >>> >>> On cleo we still get these errors with icc , looks like icc doesn't like our >>> asm code >>> >>> m4 -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_add_n -DPIC add_n.asm >>>>tmp-add_n.s >>> /bin/sh ../libtool --mode=compile --tag=CC >>> /home/jasonmoxham/mpir/mpir/trunk/mpn/m4-ccas --m4="m4" >>> icc -c99 -c -DHAVE_CONFIG_H -no-gcc -O3 -D__GMP_WITHIN_GMP >>> -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_`echo >>> sub_n | sed 's/_$//'` -I. -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> `test -f 'sub_n.asm' || >>> echo '/home/jasonmoxham/mpir/mpir/trunk/mpn/'`sub_n.asm >>> >>> icc -c99 -c -DHAVE_CONFIG_H -no-gcc -O3 -D__GMP_WITHIN_GMP >>> -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_add_n -I. >>> -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> tmp-add_n.s -DPIC -o .libs/add_n.o >>> icc: command line remark #10010: option '-c99' is deprecated and will be >>> removed in a future release. See '-help deprecated' >>> >>> icc -c99 -DHAVE_CONFIG_H -I. -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> -D__GMP_WITHIN_GMP -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_sub_1 >>> -no-gcc -O3 -c >>> sub_1.c -DPIC -o .libs/sub_1.o >>> /tmp/cleo/mpn/tmp-add_n.s(115) : error A2180: potential Write-after-Write >>> register dependency violation with /tmp/cleo/mpn/tmp-add_n.s(114),r19 >>> /tmp/cleo/mpn/tmp-add_n.s(121) : error A2180: potential Write-after-Write >>> register dependency violation with /tmp/cleo/mpn/tmp-add_n.s(118),p8 >>> /tmp/cleo/mpn/tmp-add_n.s(121) : error A2180: potential Write-after-Write >>> register dependency violation with /tmp/cleo/mpn/tmp-add_n.s(118),p9 >>> .libs/add_n.o - 3 error(s), 0 warning(s) >>> make[2]: *** [add_n.lo] Error 1 >>> make[2]: *** Waiting for unfinished jobs.... >>> icc: command line remark #10010: option '-c99' is deprecated and will be >>> removed in a future release. See '-help deprecated' >>> >>> icc -c99 -DHAVE_CONFIG_H -I. -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> -D__GMP_WITHIN_GMP -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_sub >>> -no-gcc -O3 -c >>> sub.c -DPIC -o .libs/sub.o >>> icc: command line remark #10010: option '-c99' is deprecated and will be >>> removed in a future release. See '-help deprecated' >>> /home/jasonmoxham/mpir/mpir/trunk/mpn/m4-ccas --m4=m4 >>> icc -c99 -c -DHAVE_CONFIG_H -no-gcc -O3 -D__GMP_WITHIN_GMP >>> -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_sub_n -I. >>> -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> sub_n.asm -DPIC -o .libs/sub_n.o >>> m4 -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_sub_n -DPIC sub_n.asm >>>>tmp-sub_n.s >>> >>> icc -c99 -c -DHAVE_CONFIG_H -no-gcc -O3 -D__GMP_WITHIN_GMP >>> -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_sub_n -I. >>> -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> tmp-sub_n.s -DPIC -o .libs/sub_n.o >>> icc: command line remark #10010: option '-c99' is deprecated and will be >>> removed in a future release. See '-help deprecated' >>> >>> icc -c99 -DHAVE_CONFIG_H -I. -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> -D__GMP_WITHIN_GMP -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_sub_1 >>> -no-gcc -O3 -c >>> sub_1.c -o sub_1.o >/dev/null 2>&1 >>> /tmp/cleo/mpn/tmp-sub_n.s(115) : error A2180: potential Write-after-Write >>> register dependency violation with /tmp/cleo/mpn/tmp-sub_n.s(114),r19 >>> /tmp/cleo/mpn/tmp-sub_n.s(121) : error A2180: potential Write-after-Write >>> register dependency violation with /tmp/cleo/mpn/tmp-sub_n.s(118),p8 >>> /tmp/cleo/mpn/tmp-sub_n.s(121) : error A2180: potential Write-after-Write >>> register dependency violation with /tmp/cleo/mpn/tmp-sub_n.s(118),p9 >>> .libs/sub_n.o - 3 error(s), 0 warning(s) >>> make[2]: *** [sub_n.lo] Error 1 >>> >>> icc -c99 -DHAVE_CONFIG_H -I. -I/home/jasonmoxham/mpir/mpir/trunk/mpn -I.. >>> -D__GMP_WITHIN_GMP -I/home/jasonmoxham/mpir/mpir/trunk -DOPERATION_sub >>> -no-gcc -O3 -c >>> sub.c -o sub.o >/dev/null 2>&1 >>> make[2]: Leaving directory `/tmp/cleo/mpn' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory `/tmp/cleo' >>> make: *** [all] Error 2 >>> FAILED with options icc icc >>> >>> >>> On Saturday 30 May 2009 14:50:28 Jason Moxham wrote: >>>> On Saturday 30 May 2009 14:40:50 Jason Martin wrote: >>>> > I think that icc is only available on the redhat Itanium (cleo). It >>>> > probably won't be in the path on iras. >>>> >>>> Yeah , it's not on iras , the error was on cleo , looks like a wrong path >>>> libimf is at >>>> >>>> /usr/local/intel-11.0.081/ia64-Linux-rhel/lib/ia64/libimf.a >>>> ./usr/local/intel-11.0.081/ia64-Linux-rhel/lib/ia64/libimf.so >>>> ./usr/local/intel-11.0.081/ia64-Linux-rhel/lib/ia64/libimf.so.6 >>>> >>>> and the skynet bash profile is >>>> if [ `/bin/hostname` == "cleo" ]; then >>>> PATH=/usr/local/bin/ia64-Linux-rhel:$PATH >>>> export PATH >>>> >>>> LD_LIBRARY_PATH=/usr/local/gcc-4.4.0/ia64-Linux-rhel/lib >>>> export LD_LIBRARY_PATH >>>> >>>> SAGE_FORTRAN=/usr/local/gcc-4.4.0/ia64-Linux-rhel/bin/gfortran >>>> export SAGE_FORTRAN >>>> >>>> SAGE_FORTRAN_LIB=/usr/local/gcc-4.4.0/ia64-Linux-rhel/lib/libgfortran.so >>>> export SAGE_FORTRAN_LIB >>>> >>>> >>>> PYTHONPATH=/usr/local/zope.interface-3.3.0/ia64-Linux-rhel5/lib/python:/usr >>>>/local/Twisted-8.1.0/ia64-Linux-rhel5/lib/python:/usr/local/buildbot-0.7.9/i >>>>a64-Linux-rhel5/lib/python: $PYTHONPATH >>>> export PYTHONPATH >>>> >>>> # source /usr/local/intel-11.0.081/ia64-Linux-rhel/bin/iccvars.sh ia64 >>>> # source /usr/local/intel-11.0.081/ia64-Linux-rhel/bin/ifortvars.sh ia64 >>>> >>>> fi >>>> >>>> not sure what the commented out stuff is ment to do >>>> >>>> Jason >>>> >>>> > --jason >>>> > >>>> > Jason Worth Martin >>>> > Asst. Professor of Mathematics >>>> > http://www.math.jmu.edu/~martin >>>> > >>>> > On Sat, May 30, 2009 at 9:16 AM, Jason Moxham <[email protected]> >>>> >>>> wrote: >>>> > > export CC=icc && configure >>>> > > >>>> > > fails with >>>> > > >>>> > > checking build system type... ./dummy-10941: error while loading shared >>>> > > libraries: libimf.so.6: cannot open shared object file: No such file or >>>> > > directory >>>> > > ia64-unknown-linux-gnu >>>> > > checking host system type... ia64-unknown-linux-gnu >>>> > > checking for a BSD-compatible install... /usr/bin/install -c >>>> > > checking whether build environment is sane... yes >>>> > > checking for gawk... gawk >>>> > > checking whether make sets $(MAKE)... yes >>>> > > checking whether to enable maintainer-specific portions of Makefiles... >>>> > > no checking ABI=64 >>>> > > checking compiler icc -no-gcc ... no, program does not run >>>> > > configure: error: could not find a working compiler, see config.log for >>>> > > details >>>> > > >>>> > > I use the standard skynet_bash_profile so I assume the paths are >>>> > > correct and export CC=icc is how you use the intel compiler. >>>> > > >>>> > > Jason >>>> > > >>>> > > On Saturday 30 May 2009 13:25:22 Jason Martin wrote: >>>> > >> Do we really need to support gcc-4.1 on Itanium? >>>> > >> >>>> > >> It seems like Mariah has gcc-4.4 and icc working for Itanium, so can >>>> > >> we just target those compilers and not worry about ancient gcc >>>> > >> versions? >>>> > >> >>>> > >> Jason Worth Martin >>>> > >> Asst. Professor of Mathematics >>>> > >> http://www.math.jmu.edu/~martin >>>> >>>> >>> >>> >>> > >>> >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
