A workaround for this problem would be to change the selected timer
after configure in 'ompi/contrib/vt/vt/config.h'.
To do this, just replace the line
#define TIMER TIMER_CYCLE_COUNTER
by
#define TIMER TIMER_GETTIMEOFDAY
I agree with Paul - the correct solution would be to choose the cycle
counter only if it's ensured that the platform support this.
I'll fix the faulty timer selection in the VT configure as soon as
possible.
Matthias
On Wed, 2009-01-21 at 13:25 -0800, Paul H. Hargrove wrote:
> Can't speak officially for the VT folks, but it looks like the following
> bits in ompi/vt/vt/acinclude.m4 needs to list SPARC and Alpha (maybe
> ARM?) along side MIPS as gettimeofday() platforms. Alternatively
> (perhaps preferred) one should turn this around to explicitly list the
> platforms that *do* have cycle counter support (ppc64, ppc32, ia64, x86
> IIRC) rather than listing those that don't.
>
> -Paul
>
> case $PLATFORM in
> linux)
> AC_DEFINE([TIMER_GETTIMEOFDAY], [1], [Use `gettimeofday'
> function])
> AC_DEFINE([TIMER_CLOCK_GETTIME], [2], [Use
> `clock_gettime' function])
> case $host_cpu in
> mips*)
> AC_DEFINE([TIMER], [TIMER_GETTIMEOFDAY],
> [Use timer (see below)])
> AC_MSG_NOTICE([selected timer:
> TIMER_GETTIMEOFDAY])
> ;;
> *)
> AC_DEFINE([TIMER_CYCLE_COUNTER], [3],
> [Cycle counter (e.g. TSC)])
> AC_DEFINE([TIMER],
> [TIMER_CYCLE_COUNTER], [Use timer (see below)])
> AC_MSG_NOTICE([selected timer:
> TIMER_CYCLE_COUNTER])
> ;;
> esac
> ;;
>
>
> Jeff Squyres wrote:
> > The Debian OMPI maintainers raised a few failures on some of their
> > architectures to my attention -- it looks like there's some wonkyness
> > on Debian on SPARC and Alpha -- scroll to the bottom of these two pages:
> >
> > http://buildd.debian.org/fetch.cgi?&pkg=openmpi&ver=1.3-1&arch=sparc&stamp=1232513504&file=log
> >
> >
> > http://buildd.debian.org/fetch.cgi?&pkg=openmpi&ver=1.3-1&arch=alpha&stamp=1232510796&file=log
> >
> >
> >
> > They both seem to incur the same error:
> >
> > gcc -DHAVE_CONFIG_H -I.
> > -I../../../../../../../ompi/contrib/vt/vt/vtlib -I..
> > -I../../../../../../../ompi/contrib/vt/vt/tools/opari/lib
> > -I../../../../../../../ompi/contrib/vt/vt/extlib/otf/otflib
> > -I../extlib/otf/otflib -I../../../../../../../ompi/contrib/vt/vt
> > -D_GNU_SOURCE -DBINDIR=\"/usr/bin\"
> > -DDATADIR=\"/usr/share/vampirtrace\" -DRFG -DVT_MEMHOOK -DVT_IOWRAP
> > -Wall -g -O2 -MT vt_pform_linux.o -MD -MP -MF .deps/vt_pform_linux.Tpo
> > -c -o vt_pform_linux.o
> > ../../../../../../../ompi/contrib/vt/vt/vtlib/vt_pform_linux.c
> > ../../../../../../../ompi/contrib/vt/vt/vtlib/vt_pform_linux.c: In
> > function 'vt_pform_wtime':
> > ../../../../../../../ompi/contrib/vt/vt/vtlib/vt_pform_linux.c:179:
> > error: impossible constraint in 'asm'
> > make[6]: *** [vt_pform_linux.o] Error 1
> > make[6]: Leaving directory
> > `/build/buildd/openmpi-1.3/build/shared/ompi/contrib/vt/vt/vtlib'
> >
> > VT guys -- any ideas?
> >
>
>
