This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [build] Support libgo on Solaris 2
- From: Ian Lance Taylor <iant at google dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 12 Jan 2011 10:59:32 -0800
- Subject: Re: [build] Support libgo on Solaris 2
- References: <m3y66rnuku.fsf@pepe.airs.com>
> From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
> Date: Mon, 10 Jan 2011 16:23:05 +0100
>
>>> Only defined in libgo/syscalls/syscall_linux_*.go, probably need 4 files:
>>>
>>> syscall_solaris_{386, amd64, sparc, sparcv9}.go
>>>
>>> What is syscall.ARCH supposed to be anyway? I.e. how would I handle
>>>
>>> Solaris/SPARC (always 64-bit kernel), 32 or 64-bit binaries
>>> Solaris/x86 (32 or 64-bit kernel), 32 or 64-bit binaries
>>
>> The possible values for syscall.ARCH today are: 386, amd64, arm. For
>> SPARC we can pick whatever we want, presumably sparc32 and sparc64 or
>> something like that. For x86 it should be 386 or amd64.
>
> I'd go for the customary sparc (32-bit SPARC) vs. sparcv9 (64-bit SPARC)
> here, though I still don't fully understand the semantics of
> GOARCH/syscall.ARCH: I suppose it depends on the multilib used,
> i.e. i?86-*-* and x86_64-*-* -m32 are 386, i?86-*-* and x86_64-*-* are
> amd64?
On the golang-dev list there is a bit of a push for sparc64 rather than
sparcv9. What does uname -m print on 64-bit SPARC systems? Is it the
same or different for Solaris and GNU/Linux?
Ian