Difference between pages "Talk:Coding Standards" and "Amd64-jaguar"

(Difference between pages)
(I put some comments of my own.)
 
 
Line 1: Line 1:
Screens may be able to handle more than 80 characters. Printers don't, and people do like to print out code from time to time to look at on paper. So, go bigger than 80 characters when you need to, not just because you can. There are usually ways to make it fit. Long lines can also indicate you are doing something too complex, so maybe it should be split into its own method or function.
+
{{Subarch
 +
|CPU Family=64-Bit AMD Processors
 +
|subarch=amd64-jaguar
 +
|CHOST=x86_64-pc-linux-gnu
 +
|CFLAGS=-march=btver2 -O2 -pipe
 +
|USE=mmx sse sse2 sse3 sse4 3dnow 3dnowext
 +
|CPU Features=low-power
 +
|Description=
 +
}}
 +
The '''amd64-jaguar''' (also called AMD Family 16h) subarch supports the  [[Wikipedia:Jaguar (microarchitecture)|AMD jaguar microarchitecture]], which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the [[Wikipedia:Playstation 4|Playstation 4]] and [[Wikipedia:Xbox One|Xbox One]], which each use custom 8-core Jaguar APUs.
 +
Socketed Jaguar APUs use the [[Wikipedia:AM1 Socket|AM1 socket]], and  [[Wikipedia:Socket_FT3|FT3 socket]] for mobile devices. G-series [[Wikipedia:System_on_a_chip|"system on a chip" (SoC)]] APUs are available for non-socketed devices such as tablets and embedded system boards.
  
I don't personally have a bias in general regarding tabs or spaces. Things are bound to mess up either way. However, I do prefer sticking with the the language's preferred convention if there is one. In the case of Python, that is spaces where an indent consists of four spaces. This makes for consistency when you work with integrating external code, which should generally follow the established convention of the language.
+
Desktop Jaguar APUs include the [[Wikipedia:List_of_AMD_accelerated_processing_unit_microprocessors#.22Kabini.22.2C_.22Temash.22_.282013.2C_28_nm.29|Kabini A-series APUs and Temash E-series APUs]], such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.
  
I never originally knew what they were, but many editors have mode lines. I suggest including them. This communicates the formatting preference in the document, and many text editors support them to some degree.
+
Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.
 
+
--[[User:Brantgurga|Brantgurga]] 03:29, 29 December 2010 (CET)
+

Revision as of 07:03, December 20, 2014

amd64-jaguar (Sub-architecture)

Note

This page describes a sub-architecture for Funtoo Linux, which is a particular set of optimizations that is used for a Funtoo Linux build.

CPU Family64-Bit AMD Processors
CHOSTx86_64-pc-linux-gnu
CFLAGS-march=btver2 -O2 -pipe
USEmmx sse sse2 sse3 sse4 3dnow 3dnowext
Summary


The amd64-jaguar (also called AMD Family 16h) subarch supports the AMD jaguar microarchitecture, which is targeted at low-power devices, including notebooks, tablets and small form-factor desktops and servers. It is perhaps most well-known for being the microarchitecture used for the Playstation 4 and Xbox One, which each use custom 8-core Jaguar APUs. Socketed Jaguar APUs use the AM1 socket, and FT3 socket for mobile devices. G-series "system on a chip" (SoC) APUs are available for non-socketed devices such as tablets and embedded system boards.

Desktop Jaguar APUs include the Kabini A-series APUs and Temash E-series APUs, such as the Athlon 5150 and 5350 APUs, and Sempron 2650 and 3850.

Amd64-jaguar subarches use the MOVBE instruction which is not available on amd64-bulldozer, amd64-piledriver or amd64-steamroller. They are thus not instruction-compatible with any of these subarches.