On Sun, 13 Apr 2008, James E Keenan wrote:
> I recently obtained shell accounts on some Solaris boxes. Today I made my
> first attempt to compile and build Parrot on one of them.
> 'myconfig' and the output of uname are attached.
> [parrot] 52 $ uname -a
> SunOS 5.10 Generic_120011-14 sun4v sparc SUNW,Sun-Fire-T1000
I'm not familiar with this hardware, but a few of the compilation
probes looked odd to me.
> [parrot] 53 $ cat myconfig
> Summary of my parrot 0.6.0 (r0) configuration:
> configdate='Sun Apr 13 13:52:28 2008 GMT'
> Platform:
> osname=solaris, archname=sun4-solaris-64int
> jitcapable=0, jitarchname=nojit,
> jitosname=solaris, jitcpuarch=sun4
> Compiler:
> cc='/opt/SUNWspro/bin/cc', ccflags='-I/usr/local/include
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHASATTRIBUTE_CONST
> -DHASATTRIBUTE_FORMAT -DHASATTRIBUTE_MALLOC -DHASATTRIBUTE_NONNULL
> -DHASATTRIBUTE_NORETURN -DHASATTRIBUTE_PURE -DHASATTRIBUTE_UNUSED ',
What version of the compiler is this? (You can check with "cc -V".) I
didn't know that Sun's compilers supported those attributes.
Types:
iv=long, intvalsize=4, intsize=4, opcode_t=long, opcode_t_size=4,
ptrsize=4, ptr_alignment=1 byteorder=4321,
nv=double, numvalsize=8, doublesize=8
The ptr_alignment=1 also surprises me. SPARC chips have traditionally
had ptr_alignment=4 (at least in the 32-bit mode you're using here).
It may well be correct, but I'd also be tempted to look at the cc man
page and see if there are any flags that could or should be set to make
the compiler choose an alignment appropriate for the architecture. It
may be that something like
perl Configure.pl --optimize='-xtarget=native'
will allow the compiler to choose the optimal alignment and it might
improve performance measurably. (Or it could be that this doesn't make
much of a difference anymore, the way it used to with older SPARCs.)
It may also be worthwhile to run Configure.pl in verbose mode (or even
run them by hand) to check how each of those alignment tests is passing.
--
Andy Dougherty [EMAIL PROTECTED]
