Home Wiki > openSUSE:SPARC
Sign up | Login


tagline: From openSUSE

Introduction to SPARC configurations

Common practices on SPARC are a little different than on AMD64. Whereas AMD64 is tuned towards at least keeping the speed, the common RISC chips don't specifically do anything in that regard, and so, 64 bit is said to be somewhat more expensive (cf. http://www.osnews.com/story/5768 ). As such, the majority of binaries in common userspace installation is comprised of ELF32 binaries. Unlike x86 however, it seems one can still issue 64-bit SPARC instructions (part of the SPARCv9 instruction set) not only from ELF64 binaries, but also from ELF32. Thus there are a number of configurations defined, shown in the table below. I added x86 at the end for a comparison.

Insn.Set Arch. ELF type RPM "arch" type autoconf triple typical hardware
SPARCv7 ELF32 sparc sparc-linux-gnu
SPARCv8 ELF32 sparcv8 sparcv8-linux-gnu LEON
SPARCv9/sun4u ELF32 sparcv9 sparcv9-linux-gnu Sun E250, Fujitsu SPARC64 V–VIII, Sun/Oracle/Fujitsu M series
SPARCv9/sun4u ELF64 sparc64 sparc64-linux-gnu Sun E250, Fujitus SPARC64 V–VIII, Sun/Oracle/Fujitsu M series
SPARCv9/sun4v ELF32 sparcv9v sparcv9-linux-gnu + CFLAGS=-mcpu=niagara Sun/Oracle/Fujitsu SPARC T series
SPARCv9/sun4v ELF64 sparc64v sparc64-linux-gnu + CFLAGS=-mcpu=niagara Sun/Oracle/Fujitsu SPARC T series
i686 ELF32 i686 i686-linux-gnu
AMD64 ELF64 x86_64 x86_64-linux-gnu


The repositories thus provide the following: sparcv9, sparc64

Supported hardware thus: All 64-bit UltraSPARC/SPARCv9 compatible silicon.

Maintainer: j.eng

Known bugs

  • an installer image is currently absent (sort of the last piece in the puzzle)
  • zypper does not pick the intuitively-correct architecture at this point

Build Service

Located at http://build.inai.de/ (anon support incomplete atm). BSAPI remoteurl is http://api.inai.de/public .

Build Servers

ares Fujitsu SPARC Enterprise T1000, 24 1.0GHz thread Niagara-1 CPU, 2000 GB SATA, 8GB RAM.