The SPARC port uses the
sparc keyword. It focuses on
hardware (Sun UltraSparc systems with
and 2.4 kernels should still work with Gentoo, but they are no longer supported
by the Gentoo/SPARC team.
v9 systems use a pure 64 bit kernel and a pure 32 bit userland. This can
cause portability problems when working with low level software if the kernel
does not provide working 32 bit compatibility interfaces.
v8 systems use a pure 32 bit kernel and a pure 32 bit userland.
All of the above SPARC systems are big endian, nevertheless the
architecture also utilizes little-endian instructions to access data on PCI
For a package to have the
~sparc keyword added, the following additional
items must generally hold:
It is generally expected that anyone who does keywording for SPARC should be on
There are three basic SPARC instruction set standards.
v7is the original instruction set used in very old hardware. Gentoo does not ship
v7capable stages, however a sufficiently crazy person could in theory run Gentoo on a
v8is an extension of
v7with added support for hardware integer multiplication and division. Last time Gentoo sparc32 (
sun4m) stages were available was on 2006.1 release.
v9adds in 64 bit support and a large number of performance-enhancing features. Gentoo sparc64 (
sun4u) stages are
In addition, individual CPU implementations have slight differences — for example, HyperSparc CPUs have relaxed requirements when it comes to scheduling certain instructions. These are relatively minor differences.
gcc is invoked without any
-mcpu parameter, it will generate
code. Depending upon the application, this can be anywhere up to five times
v9 code when running on an UltraSparc
graphics applications which make heavy use of integer multiplication and
division are especially badly hit. For this reason, the comments in
Not Filtering Variables
are especially important on SPARC.
The SPARC team can be contacted:
#gentoo-sparcIRC channel on Freenode