mirror of
https://git.yoctoproject.org/poky
synced 2026-04-17 09:32:12 +02:00
dev-manual, concepts-manual: Moved x32 section
I had split up the section on x32 into a concept piece and a "how-to" piece earlier in order to satisfy outside pressure to isolate all "how-to" stuff in the dev-manual. Doing this put a "conceptual" blurb about x32 in the new concepts-manual. It has been decided that x32 is not a concept. It really does not fit into the ref-manual either. So, I have re-combined the intro blurb of the x32 stuff back as the beginning piece of the "Usingt x32 psABI" section in the dev-manual. (From yocto-docs rev: 6e8240cc1a90a8d78ff456d3138c525eceea3ee3) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
505a31c1a1
commit
35549a7a45
@@ -3643,72 +3643,6 @@
|
||||
</section>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section id='x32'>
|
||||
<title>x32 psABI</title>
|
||||
|
||||
<para>
|
||||
x32 processor-specific Application Binary Interface
|
||||
(<ulink url='https://software.intel.com/en-us/node/628948'>x32 psABI</ulink>)
|
||||
is a native 32-bit processor-specific ABI for
|
||||
<trademark class='registered'>Intel</trademark> 64 (x86-64)
|
||||
architectures.
|
||||
An ABI defines the calling conventions between functions in a
|
||||
processing environment.
|
||||
The interface determines what registers are used and what the sizes are
|
||||
for various C data types.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Some processing environments prefer using 32-bit applications even
|
||||
when running on Intel 64-bit platforms.
|
||||
Consider the i386 psABI, which is a very old 32-bit ABI for Intel
|
||||
64-bit platforms.
|
||||
The i386 psABI does not provide efficient use and access of the
|
||||
Intel 64-bit processor resources, leaving the system underutilized.
|
||||
Now consider the x86_64 psABI.
|
||||
This ABI is newer and uses 64-bits for data sizes and program
|
||||
pointers.
|
||||
The extra bits increase the footprint size of the programs,
|
||||
libraries, and also increases the memory and file system size
|
||||
requirements.
|
||||
Executing under the x32 psABI enables user programs to utilize CPU
|
||||
and system resources more efficiently while keeping the memory
|
||||
footprint of the applications low.
|
||||
Extra bits are used for registers but not for addressing mechanisms.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The Yocto Project supports the final specifications of x32 psABI
|
||||
as follows:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
You can create packages and images in x32 psABI format on
|
||||
x86_64 architecture targets.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
You can successfully build recipes with the x32 toolchain.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
You can create and boot
|
||||
<filename>core-image-minimal</filename> and
|
||||
<filename>core-image-sato</filename> images.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
RPM Package Manager (RPM) support exists for x32 binaries.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Support for large images exists.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For steps on how to use x32 psABI, see the
|
||||
"<ulink url='&YOCTO_DOCS_DEV_URL;#using-x32-psabi'>Using x32 psABI</ulink>"
|
||||
section in the Yocto Project Development Tasks Manual.
|
||||
</para>
|
||||
</section>
|
||||
</chapter>
|
||||
<!--
|
||||
vim: expandtab tw=80 ts=4
|
||||
|
||||
@@ -4799,11 +4799,57 @@
|
||||
is a native 32-bit processor-specific ABI for
|
||||
<trademark class='registered'>Intel</trademark> 64 (x86-64)
|
||||
architectures.
|
||||
<note>
|
||||
For more information on x32 psABI, see the
|
||||
"<ulink url='&YOCTO_DOCS_CM_URL;#x32'>x32 psABI</ulink>"
|
||||
section in the Yocto Project Concepts Manual.
|
||||
</note>
|
||||
An ABI defines the calling conventions between functions in a
|
||||
processing environment.
|
||||
The interface determines what registers are used and what the
|
||||
sizes are for various C data types.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Some processing environments prefer using 32-bit applications even
|
||||
when running on Intel 64-bit platforms.
|
||||
Consider the i386 psABI, which is a very old 32-bit ABI for Intel
|
||||
64-bit platforms.
|
||||
The i386 psABI does not provide efficient use and access of the
|
||||
Intel 64-bit processor resources, leaving the system underutilized.
|
||||
Now consider the x86_64 psABI.
|
||||
This ABI is newer and uses 64-bits for data sizes and program
|
||||
pointers.
|
||||
The extra bits increase the footprint size of the programs,
|
||||
libraries, and also increases the memory and file system size
|
||||
requirements.
|
||||
Executing under the x32 psABI enables user programs to utilize CPU
|
||||
and system resources more efficiently while keeping the memory
|
||||
footprint of the applications low.
|
||||
Extra bits are used for registers but not for addressing mechanisms.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The Yocto Project supports the final specifications of x32 psABI
|
||||
as follows:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
You can create packages and images in x32 psABI format on
|
||||
x86_64 architecture targets.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
You can successfully build recipes with the x32 toolchain.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
You can create and boot
|
||||
<filename>core-image-minimal</filename> and
|
||||
<filename>core-image-sato</filename> images.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
RPM Package Manager (RPM) support exists for x32 binaries.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Support for large images exists.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To use the x32 psABI, you need to edit your
|
||||
<filename>conf/local.conf</filename> configuration file as
|
||||
follows:
|
||||
|
||||
Reference in New Issue
Block a user