Outline ·
[ Standard ] ·
Linear+
Intel proposes dropping 16 and 32-bit support, Start to develop pure 64bit apps ?
|
MatQuasar
|
Jul 19 2023, 10:22 PM
|
|
QUOTE(flashang @ Jul 19 2023, 11:15 AM) For memory, may be after 64 bit addressing is no enough... Last time I encounter 64-bit address is not all accessible, only 40-bit address, and need some tweaks to access all 64-bit memory.... Then when doing bootloader also I encounter A20 line, or else cannot access full width of memory address (not sure how many bits)..... That's when I start pening pening kepala, give up studying the width of bus, memory address...
|
|
|
|
|
|
MatQuasar
|
Jul 25 2023, 08:10 PM
|
|
APX! https://www.intel.com/content/www/us/en/dev...nsions-apx.htmlQUOTE Intel® architecture powers datacenters and personal computers around the world. Since its introduction by Intel® in 1978, the architecture has continuously evolved to take advantage of emerging workloads and the relentless pace of Moore’s law. The original instruction set defined only eight 16-bit general-purpose registers, which over the years were doubled in number and quadrupled in size. A large set of vector registers was added, and most recently Intel® AMX introduced two-dimensional matrix registers, providing a big jump in AI performance.1
Today, we are introducing the next major step in the evolution of Intel® architecture. Intel® Advanced Performance Extensions (Intel® APX) expands the entire x86 instruction set with access to more registers and adds various new features that improve general-purpose performance. The extensions are designed to provide efficient performance gains across a variety of workloads – without significantly increasing silicon area or power consumption of the core.
Intel® APX doubles the number of general-purpose registers (GPRs) from 16 to 32. This allows the compiler to keep more values in registers; as a result, APX-compiled code contains 10% fewer loads and more than 20% fewer stores than the same code compiled for an Intel® 64 baseline.2 Register accesses are not only faster, but they also consume significantly less dynamic power than complex load and store operations This post has been edited by MatQuasar: Jul 25 2023, 08:13 PM
|
|
|
|
|
|
MatQuasar
|
Jul 25 2023, 08:12 PM
|
|
QUOTE(narf03 @ Jul 19 2023, 01:19 AM) each bit extra is twice the capacity, i wonder when we will move towards 128 bit. As @flashang said, now we have 512-bit vector registers, although general purpose registers are only 64-bit.
|
|
|
|
|
|
MatQuasar
|
Sep 4 2023, 09:33 PM
|
|
QUOTE(flashang @ Jul 19 2023, 11:28 PM) 40 bit address can handle up to 1 TB (some system is 48 bit up to 256 TB),  Thank you for inspiring me, I took note of the following: I just aware that although PE32+ uses QWORD runtime address in memory, but in reality it will never use up all the high order DWORD, because even 40-bit address is enough for 1TB RAM. Image base in PE32+ may starts with 0x0000 0001 xxxx xxxx (The QWORD address above is 36-bit)
|
|
|
|
|
|
MatQuasar
|
Sep 4 2023, 09:34 PM
|
|
QUOTE(flashang @ Jul 19 2023, 11:28 PM) 40 bit address can handle up to 1 TB (some system is 48 bit up to 256 TB),  Thank you for inspiring me, I took note of the following: I just aware that although PE32+ uses QWORD runtime address in memory, but in reality it will never use up all the high order DWORD, because even 40-bit address is enough for 1TB RAM. Image base in PE32+ may starts with 0x0000 0001 xxxx xxxx (The QWORD address above is 36-bit)
|
|
|
|
|