>I ran into this myself yesterday. I couldn't figure out a definitive
>answer, because I am no expert on the SPARC architecture, but it appears
>that at least on an UltraSparc IIi machine from a few years ago, the
>"sparc V9" instructions are supported. However, the gcc by default
>doesn't define __sparc_v9__ on that architecture. There are some -m
>flags that can be passed to gcc (like multisparc, etc.), but I'm not
>sure for what host machines they are appropriate exactly. Perhaps the
>SPARC experts on the list can comment more, but in the meantime, the
>following simple (but likely incorrect) patch worked fine for me:
Well, at least my gcc defines __sparc_v9__ if cpu is either v9, ultrasparc
or ultrasparc3:
%{mcpu=v9:-D__sparc_v9__} %{mcpu=ultrasparc:-D__sparc_v9__}
%{mcpu=ultrasparc3:-D__sparc_v9__}
This is from /usr/lib/gcc-lib/sparc-linux/3.3.5/specs. What does your
compiler define, as you still can compile the RDTICK instruction in the
#ifdef section? RDTICK is not available on V8 (Sparc32) architecture, only
on V9.
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/