All are based on a Linux system running on a PowerPC processor.
它们全都是基于运行在PowerPc处理器上的Linux系统。
First, that Mac OS X 10.6 would drop support for PowerPC-based Macs.
第一，MacOSX10.6将会抛弃对基于PowerPC的Mac的支持。
All PowerPC programs start off with a pointer to this stack in register 1.
所有的PowerPC程序都需要由一个指向寄存器1中的这个堆栈的指针启动。
You've now downloaded and started your first PowerPC program inside an FPGA.
现在已经在FPGA内下载并启动了您的第一个PowerPC程序。
The PowerPC has 15 different instruction formats, many with several subformats.
PowerPC具有15种不同的指令格式，很多指令格式都有几种子格式。
The solution is to instruct the JIT to produce a set of PowerPC 604 instructions.
解决方案是，指示JIT生成一组PowerPC 604 指令。
As you can see, writing functions using the simplified PowerPC ABI is very straightforward.
正如您可以看到的一样，使用简化的PowerPCABI编写函数非常简单。
The 64-bit Power architecture contains support for the complete 32-bit PowerPC architecture.
64-位Power架构包含对完整的32 -位PowerPC架构的支持。
Some platforms (not PowerPC) allow programmers to specify a multiplier for the index register.
有些平台(非powerpc)允许程序员为索引寄存器指定一个倍数。
In other words, every PowerPC processor should be able to execute base PowerPC 604 instructions.
换句话说，每个PowerPC处理器都应该可以执行基本的PowerPC 604指令。
In retrospect, an Apple partition map is a very reasonable thing for a PowerPC Linux box to hold.
回顾一下，对于运行Linux的PowerPC机器来说，使用一个Apple分区映射是非常合理的。
Cross compilers are available for 32-bit PowerPC Linux systems and 64-bit Linux on POWER systems.
还存在可以同时在32位PowerPCLinux系统和64位LinuxonPOWER系统上运行的跨系统编译器。
On PowerPC this script takes one optional parameter, buffer_size, which is specified in Megabytes.
在PowerPC上这个脚本使用一个可选参数buffer_size，它的单位是MB。
This would give the company volume for its PowerPC devices and leverage for other PowerPC offerings.
这将会让公司有能力开发PowerPC设备，提高其他相关产品的研发水平。
You must build the kernel in 64-bit mode since the 32-bit kernel is not supported on SLES 8 for PowerPC.
您必须以64位模式编译内核，因为用于PowerPC的SLES8不支持32位内核。
Registers in the PowerPC ABI are divided into three basic classes: dedicated, volatile, and non-volatile.
PowerPCABI中的寄存器被划分成3种基本类型：专用寄存器、易失性寄存器和非易失性寄存器。
The only constraint is that the operating system must support the underlying hardware (for example, PowerPC).
惟一的限制是操作系统必须要支持底层硬件（例如PowerPC）。
Other architectures supported in this mode include ARM, SPARC, and PowerPC, though more are under development.
这种模式支持的其他体系结构还包括ARM、SPARC和PowerPC，而且还有很多尚在开发之中。
Often this is not needed because of the large number of registers available for use in the PowerPC architecture.
通常这并不需要，因为在PowerPC体系结构中有大量寄存器可以使用。
This program runs fine on both x86 and PowerPC, but dies on the Power system when compiled with the -m64 option.
这个程序在x86和PowerPC 上都可以很好地运行，不过在Power系统上使用-m64 选项进行编译时就会死掉。
When a function is called using the PowerPC ABI semantics, it passes the parameters to the function in registers.
在使用PowerPCabi语义调用一个函数时，它会使用寄存器将自己的参数传递给函数。
The PowerPC ABI actually puts the storage space for the function parameters in the calling function's stack space.
PowerPCABI实际上会将函数参数使用的存储空间放入调用函数的堆栈空间中。
Indeed, it's possible for an application binary to contain both 32-bit and 64-bit versions for Intel and PowerPC Macs.
事实上，对于Intel和PowerPC Mac，应用程序二进制有可能包含32位和64位两种版本。
The next article gets down to starting up the processor core, writing some actual PowerPC code, and wiggling some pins!
下一篇文章将着手介绍启动处理器核心、编写一些实际的PowerPC代码并处理一些pin ！
The PPE, although architecturally similar to other 64-bit PowerPC chips, isn't directly related to a specific product line.
尽管PPE从体系结构上来说与其他64位PowerPC芯片非常类似，但它与任何一条特定的生产线都没有任何直接的联系。
There are also VMX vector extensions for the IBM PowerPC 970 processor that can increase the performance of vectorized code.
另外也有用于IBMPowerPC 970处理器的VMX向量扩展，可以提高向量化代码的性能。
One example is the Apple G4 processor, Motorola 7400, which is generically classified as belonging to the PowerPC 700 family.
举一个例子，AppleG4处理器，Motorola 7400，通常被分类到PowerPC 700家族。
Fabricated with 90-nanometer low-power CMOS technology, the 32-bit PowerPC e300-based multimedia SoC is clockable up to 400MHz.
这个基于PowerPCe300的32位多媒体SoC采用90纳米的低功耗CMOS技术制程，时钟频率400MHz。
But what happens if a client running on a big endian IBM PowerPC attempts to send a 32-bit integer to a little endian Intel x86?
但是，如果一个运行在高位优先的IBMPowerPC上的客户端发送一个32位的整数到一个低位优先的Intelx86，那将会发生什么呢？
Binary compatibility between 32-bit applications running in native 32-bit PowerPC environments and 64-bit POWER environments exists.
在本地32-位PowerPC环境以及64 -位POWER环境中运行的32 -位应用程序之间存在二进制兼容性。
应用推荐