如果您想要在应用程序将要支持的所有体系结构上保持通用的起始地址，那么在确定那个地址之前必须考虑所有的体系结构。
You have to consider all architectures before deciding on the addresses if you want to keep the starting addresses common for all the architectures that are going to be supported by the application.
缺点是，32位的程序必须认识这种分段体系结构，才能充分利用32位地址空间。
Of the disadvantages, a 32-bit program must be cognizant of the segmented architecture to take full advantage of the 32-bit address space.
在这种体系结构中，对于所有平台，每个进程的地址空间都是2的64次方，或者18,446,744,073GB。
With this architecture, the address space of each process is 2 to the power of 64, or 18,446,744,073 GB, on all platforms.
例如，在Intel体系结构中，每个进程将底部四分之三的地址空间分配给用户区域；顶部部分分配给内核。
For example, on Intel every process has the bottom three-quarters of the address space allocated to user land; the top piece is allocated to the kernel.
在研究此配置的细节之前，下面首先列出WebSphere ApplicationServerfor z/OS采用拆分地址空间体系结构的一些原因
Before we look at details of this configuration, here are a few reasons for the split address space architecture of WebSphere Application Server for z/OS
作者从DNS的体系结构、DNS地址解析以及在IPV4到IPV6过渡过程中DNS解决方案等几个方面对现阶段IPv6环境下的DNS系统进行分析和研究。
The paper examined and analyse DNS system in current IPV6 environment for DNS systematic set - up, DNS address resolution, DNS resolution to transition from IPV4 to IPV6.
为了解决这一问题，IETF提议通过分离终端系统标志和路由标志的地址空间来重新考虑互联网的寻址体系结构。
In order to solve this problem, proposed several solutions by IETF to address the Internet addressing architecture by separating the end-systems identifiers 'space and the routing locators 'space.
某些体系结构不允许执行指令指向目标指令的地址，真正的程序员才不管这种小小的限制。
Some candyass architectures won't allow EXECUTE instructions to address another EXECUTE instruction as the target instruction. Real Programmers despise petty restrictions.
某些体系结构不允许执行指令指向目标指令的地址，真正的程序员才不管这种小小的限制。
Some candyass architectures won't allow EXECUTE instructions to address another EXECUTE instruction as the target instruction. Real Programmers despise petty restrictions.
应用推荐