text:
x86-64
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
"AMD64" and "Intel 64" redirect here. For the Intel 64-bit architecture in Itanium chips, see IA-64.
Opteron, the first CPU to introduce the x86-64 extensions in 2003
The five-volume set of the x86-64 Architecture Programmer's Guide, as published and distributed by AMD in 2002
x86-64 (also known as x64, x86_64, AMD64 and Intel 64[note 1]) is the 64-bit version of the x86 instruction set. It introduces two new modes of operation, 64-bit mode and compatibility mode, along with a new 4-level paging mode. With 64-bit mode and the new paging mode, it supports vastly larger amounts (theoretically, 264 bytes or 16 exabytes) of virtual memory and physical memory than is possible on its 32-bit predecessors, allowing programs to store larger amounts of data in memory. x86-64 also expands general-purpose registers to 64-bit and provides numerous other enhancements. In 64-bit mode, instructions are modified to support 64-bit operands and 64-bit addressing mode. The compatibility mode allows 16- and 32-bit user applications to run unmodified coexisting with 64-bit applications if the 64-bit operating system supports them.[11][note 2] Because the full x86 16-bit and 32-bit instruction sets remain implemented in hardware without any intervening emulation, these older executables can run with little or no performance penalty,[13] while newer or modified applications can take advantage of new features of the processor design to achieve performance improvements. Also, a processor supporting x86-64 still powers on in real mode for full backward compatibility.
The original specification, created by AMD and released in 2000, has been implemented by AMD, Intel and VIA. The AMD K8 processor was the first to implement it. This was the first significant addition to the x86 architecture designed by a company other than Intel. Intel was forced to follow suit and introduced a modified NetBurst family which was software-compatible with AMD's specification. VIA Technologies introduced x86-64 in their VIA Isaiah architecture, with the VIA Nano.
The x86-64 architecture is distinct from the Intel Itanium architecture (formerly IA-64), which is not compatible on the native instruction set level with the x86 architecture.
Contents
1 AMD64
1.1 History
1.2 Implementations
1.3 Architectural features
1.4 Virtual address space details
1.4.1 Canonical form addresses
1.4.2 Page table structure
1.4.3 Operating system limits
1.5 Physical address space details
1.6 Operating modes
1.6.1 Long mode
1.6.2 Legacy mode
2 Intel 64
2.1 History
2.2 Implementations
3 VIA's x86-64 implementation
4 Differences between AMD64 and Intel 64
4.1 Recent implementations
4.2 Older implementations
5 Adoption
6 Operating system compatibility and characteristics
6.1 BSD
6.1.1 DragonFly BSD
6.1.2 FreeBSD
6.1.3 NetBSD
6.1.4 OpenBSD
6.2 DOS
6.3 Linux
6.4 macOS
6.5 Solaris
6.6 Windows
7 Video game consoles
8 Industry naming conventions
9 Licensing
10 See also
11 Notes
12 References
13 External links
AMD64[edit]
AMD64 logo
History[edit]
AMD64 was created as an alternative to the radically different IA-64 architecture, which was designed by Intel and Hewlett Packard. Originally announced in 1999[14] while a full specification became available in August 2000,[15] the AMD64 architecture was positioned by AMD from the beginning as an evolutionary way to add 64-bit computing capabilities to the existing x86 architecture, as opposed to Intel's approach of creating an entirely new 64-bit architecture with IA-64.
The first AMD64-based processor, the Opteron, was released in April 2003.
Implementations[edit]
AMD's processors implementing the AMD64 architecture include Opteron, Athlon 64, Athlon 64 X2, Athlon 64 FX, Athlon II (followed by "X2", "X3", or "X4" to indicate the number of cores, and XLT models), Turion 64, Turion 64 X2, Sempron ("Palermo" E6 stepping and all "Manila" models), Phenom (followed by "X3" or "X4" to indicate the number of cores), Phenom II (followed by "X2", "X3", "X4" or "X6" to indicate the number of cores), FX, Fusion/APU and Ryzen/Epyc.
Architectural features[edit]
The primary defining characteristic of AMD64 is the availability of 64-bit general-purpose processor registers (for example, rax and rbx), 64-bit integer arithmetic and logical operations, and 64-bit virtual addresses. The designers took the opportunity to make other improvements as well. Some of the most significant changes are described below.
64-bit integer capability
All general-purpose registers (GPRs) are expanded from 32 bits to 64 bits, and all arithmetic and logical operations, memory-to-register and register-to-memory operations, etc., can now operate directly on 64-bit integers. Pushes and pops on the stack default to 8-byte strides, and pointers are 8 bytes wide.
Additional registers
In addition to increasing the size of the general-purpose registers, the number of named general-purpose registers is increased from eight (i.e. eax, ecx, edx, ebx, esp, ebp, esi, edi) in x86 to 16 (i.e. rax, rcx, rdx, rbx, rsp, rbp, rsi, rdi, r8, r9, r10, r11, r12, r13, r14, r15). It is therefore possible to keep more local variables in registers rather than on the stack, and to let registers hold frequently accessed constants; arguments for small and fast subroutines may also be passed in registers to a greater extent.
AMD64 still has fewer registers than many RISC instruction sets (e.g. PA-RISC and MIPS have 32 GPRs; Alpha, 64-bit ARM, and SPARC have 31) or VLIW-like machines such as the IA-64 (which has 128 registers). However, an AMD64 implementation may have far more internal registers than the number of architectural registers exposed by the instruction set (see register renaming).
Additional XMM (SSE) registers
Similarly, the number of 128-bit XMM registers (used for Streaming SIMD instructions) is also increased from 8 to 16.
The traditional x87 FPU register stack is not included in the register file size extension in 64-bit mode, compared with the XMM registers used by SSE2, which did get extended. The x87 register stack is not a simple register file although it does allow direct access to individual registers by low cost exchange operations.
Larger virtual address space
The AMD64 architecture defines a 64-bit virtual address format, of which the low-order 48 bits are used in current implementations.[11](p120) This allows up to 256 TB (248 bytes) of virtual address space. The architecture definition allows this limit to be raised in future implementations to the full 64 bits,[11](p2)(p3)(p13)(p117)(p120) extending the virtual address space to 16 EB (264 bytes). This is compared to just 4 GB (232 bytes) for the x86.[16]
This means that very large files can be operated on by mapping the entire file into the process' address space (which is often much faster than working with file read/write calls), rather than having to map regions of the file into and out of the address space.
Larger physical address space
The original implementation of the AMD64 architecture implemented 40-bit physical addresses and so could address up to 1 TB (240 bytes) of RAM.[11](p24) Current implementations of the AMD64 architecture (starting from AMD 10h microarchitecture) extend this to 48-bit physical addresses[17] and therefore can address up to 256 TB of RAM. The architecture permits extending this to 52 bits in the future[11](p24)[18] (limited by the page table entry format);[11](p131) this would allow addressing of up to 4 PB of RAM. For comparison, 32-bit x86 processors are limited to 64 GB of RAM in Physical Address Extension (PAE) mode,[19] or 4 GB of RAM without PAE mode.[11](p4)
Larger physical address space in legacy mode
When operating in legacy mode the AMD64 architecture supports Physical Address Extension (PAE) mode, as do most current x86 processors, but AMD64 extends PAE from 36 bits to an architectural limit of 52 bits of physical address. Any implementation therefore allows the same physical address limit as under long mode.[11](p24)
Instruction pointer relative data access
Instructions can now reference data relative to the instruction pointer (RIP register). This makes position independent code, as is often used in shared libraries and code loaded at run time, more efficient.
SSE instructions
The original AMD64 architecture adopted Intel's SSE and SSE2 as core instructions. These instruction sets provide a vector supplement to the scalar x87 FPU, for the single-precision and double-precision data types. SSE2 also offers integer vector operations, for data types ranging from 8bit to 64bit precision. This makes the vector capabilities of the architecture on par with those of the most advanced x86 processors of its time. These instructions can also be used in 32-bit mode. The proliferation of 64-bit processors has made these vector capabilities ubiquitous in home computers, allowing the improvement of the standards of 32-bit applications. The 32-bit edition of Windows 8, for example, requires the presence of SSE2 instructions.[20] SSE3 instructions and later Streaming SIMD Extensions instruction sets are not standard features of the architecture.
No-Execute bit
The No-Execute bit or NX bit (bit 63 of the page table entry) allows the operating system to specify which pages of virtual address space can contain executable code and which cannot. An attempt to execute code from a page tagged "no execute" will result in a memory access violation, similar to an attempt to write to a read-only page. This should make it more difficult for malicious code to take control of the system via "buffer overrun" or "unchecked buffer" attacks. A similar feature has been available on x86 processors since the 80286 as an attribute of segment descriptors; however, this works only on an entire segment at a time.
Segmented addressing has long been considered an obsolete mode of operation, and all current PC operating systems in effect bypass it, setting all segments to a base address of zero and (in their 32 bit implementation) a size of 4 GB. AMD was the first x86-family vendor to implement no-execute in linear addressing mode. The feature is also available in legacy mode on AMD64 processors, and recent Intel x86 processors, when PAE is used.
Removal of older features
A few "system programming" features of the x86 architecture were either unused or underused in modern operating systems and are either not available on AMD64 in long (64-bit and compatibility) mode, or exist only in limited form. These include segmented addressing (although the FS and GS segments are retained in vestigial form for use as extra base pointers to operating system structures),[11](p70) the task state switch mechanism, and virtual 8086 mode. These features remain fully implemented in "legacy mode", allowing these processors to run 32-bit and 16-bit operating systems without modifications. Some instructions that proved to be rarely useful are not supported in 64-bit mode, including saving/restoring of segment registers on the stack, saving/restoring of all registers (PUSHA/POPA), decimal arithmetic, BOUND and INTO instructions, and "far" jumps and calls with immediate operands.
Virtual address space details[edit]
Canonical form addresses[edit]
Canonical address space implementations (diagrams not to scale)
Current 48-bit implementation
56-bit implementation
64-bit implementation
Although virtual addresses are 64 bits wide in 64-bit mode, current implementations (and all chips known to be in the planning stages) do not allow the entire virtual address space of 264 bytes (16 EB) to be used. This would be approximately four billion times the size of virtual address space on 32-bit machines. Most operating systems and applications will not need such a large address space for the foreseeable future, so implementing such wide virtual addresses would simply increase the complexity and cost of address translation with no real benefit. AMD therefore decided that, in the first implementations of the architecture, only the least significant 48 bits of a virtual address would actually be used in address translation (page table lookup).[11](p120)
In addition, the AMD specification requires that the most significant 16 bits of any virtual address, bits 48 through 63, must be copies of bit 47 (in a manner akin to sign extension). If this requirement is not met, the processor will raise an exception.[11](p131) Addresses complying with this rule are referred to as "canonical form."[11](p130) Canonical form addresses run from 0 through 00007FFF'FFFFFFFF, and from FFFF8000'00000000 through FFFFFFFF'FFFFFFFF, for a total of 256 TB of usable virtual address space. This is still 65,536 times larger than the virtual 4 GB address space of 32-bit machines.
This feature eases later scalability to true 64-bit addressing. Many operating systems (including, but not limited to, the Windows NT family) take the higher-addressed half of the address space (named kernel space) for themselves and leave the lower-addressed half (user space) for application code, user mode stacks, heaps, and other data regions.[21] The "canonical address" design ensures that every AMD64 compliant implementation has, in effect, two memory halves: the lower half starts at 00000000'00000000 and "grows upwards" as more virtual address bits become available, while the higher half is "docked" to the top of the address space and grows downwards. Also, enforcing the "canonical form" of addresses by checking the unused address bits prevents their use by the operating system in tagged pointers as flags, privilege markers, etc., as such use could become problematic when the architecture is extended to implement more virtual address bits.
The first versions of Windows for x64 did not even use the full 256 TB; they were restricted to just 8 TB of user space and 8 TB of kernel space.[21] Windows did not support the entire 48-bit address space until Windows 8.1, which was released in October 2013.[21]
Page table structure[edit]
The 64-bit addressing mode ("long mode") is a superset of Physical Address Extensions (PAE); because of this, page sizes may be 4 KB (212 bytes) or 2 MB (221 bytes).[11](p120) Long mode also supports page sizes of 1 GB (230 bytes).[11](p120) Rather than the three-level page table system used by systems in PAE mode, systems running in long mode use four levels of page table: PAE's Page-Directory Pointer Table is extended from four entries to 512, and an additional Page-Map Level 4 (PML4) Table is added, containing 512 entries in 48-bit implementations.[11](p131) A full mapping hierarchy of 4 KB pages for the whole 48-bit space would take a bit more than 512 GB of memory (about 0.195% of the 256 TB virtual space).
Intel has proposed a scheme with a five-level page table. If implemented, this would allow Intel 64 processors to support a 57-bit virtual address space.[22]
Operating system limits[edit]
The operating system can also limit the virtual address space. Details, where applicable, are given in the "Operating system compatibility and characteristics" section.
Physical address space details[edit]
Current AMD64 processors support a physical address space of up to 248 bytes of RAM, or 256 TB.[17] However, as of June 2010[update], there were no known x86-64 motherboards that support 256 TB of RAM.[23][24][25][26][not in citation given] The operating system may place additional limits on the amount of RAM that is usable or supported. Details on this point are given in the "Operating system compatibility and characteristics" section of this article.
Operating modes[edit]
The architecture has two primary modes of operation, long mode and legacy mode.
Operating mode
Operating sub-mode
Operating system required
Type of code being run
Default address size
Default operand size
Supported typical operand sizes
Register file size
Long mode 64-bit mode 64-bit 64-bit code 64 bits 32 bits 8, 16, 32, or 64 bits 16 registers per file
Compatibility mode 32-bit code 32 bits 32 bits 8, 16, or 32 bits 8 registers per file
16-bit code 16 bits 16 bits 8, 16, or 32 bits 8 registers per file
Legacy mode Protected mode 32-bit 32-bit code 32 bits 32 bits 8, 16, or 32 bits 8 registers per file
16-bit protected mode 16-bit code 16 bits 16 bits 8, 16, or 32 bits[m 1] 8 registers per file
Virtual 8086 mode 16-bit protected mode or 32-bit some of real mode code 16 bits 16 bits 8, 16, or 32 bits[m 1] 8 registers per file
Real mode 16-bit real mode real mode code 16 bits 16 bits 8, 16, or 32 bits[m 1] 8 registers per file
^ Jump up to: a b c Note that 16-bit code written for the 80286 and below does not use 32-bit operand instructions. 16-bit code written for the 80386 and above can use 32-bit operand instructions, but defaults to using 16-bit operands.
State diagram of the x86-64 operating modes
Long mode[edit]
Main article: Long mode
Long mode is the architecture's intended primary mode of operation; it is a combination of the processor's native 64-bit mode and a combined 32-bit and 16-bit compatibility mode. It is used by 64-bit operating systems. Under a 64-bit operating system, 64-bit programs run under 64-bit mode, and 32-bit and 16-bit protected mode applications (that do not need to use either real mode or virtual 8086 mode in order to execute at any time) run under compatibility mode. Real-mode programs and programs that use virtual 8086 mode at any time cannot be run in long mode unless those modes are emulated in software.[11]:11 However, such programs may be started from an operating system running in long mode on processors supporting VT-x or AMD-V by creating a virtual processor running in the desired mode.
Since the basic instruction set is the same, there is almost no performance penalty for executing protected mode x86 code. This is unlike Intel's IA-64, where differences in the underlying instruction set means that running 32-bit code must be done either in emulation of x86 (making the process slower) or with a dedicated x86 coprocessor. However, on the x86-64 platform, many x86 applications could benefit from a 64-bit recompile, due to the additional registers in 64-bit code and guaranteed SSE2-based FPU support, which a compiler can use for optimization. However, applications that regularly handle integers wider than 32 bits, such as cryptographic algorithms, will need a rewrite of the code handling the huge integers in order to take advantage of the 64-bit registers.
Legacy mode[edit]
Legacy mode is the mode used by 16-bit ("protected mode" or "real mode") and 32-bit operating systems. In this mode, the processor acts like a 32-bit x86 processor, and only 16-bit and 32-bit code can be executed. Legacy mode allows for a maximum of 32 bit virtual addressing which limits the virtual address space to 4 GB.[11](p14)(p24)(p118) 64-bit programs cannot be run from legacy mode.
Intel 64[edit]
Intel 64 is Intel's implementation of x86-64, used and implemented in various processors made by Intel.
History[edit]
Historically, AMD has developed and produced processors with instruction sets patterned after Intel's original designs, but with x86-64, roles were reversed: Intel found itself in the position of adopting the ISA which AMD had created as an extension to Intel's own x86 processor line.
Intel's project was originally codenamed Yamhill (after the Yamhill River in Oregon's Willamette Valley).[citation needed] After several years of denying its existence, Intel announced at the February 2004 IDF that the project was indeed underway. Intel's chairman at the time, Craig Barrett, admitted that this was one of their worst-kept secrets.[28][29]
Intel's name for this instruction set has changed several times. The name used at the IDF was CT (presumably[original research?] for Clackamas Technology, another codename from an Oregon river); within weeks they began referring to it as IA-32e (for IA-32 extensions) and in March 2004 unveiled the "official" name EM64T (Extended Memory 64 Technology). In late 2006 Intel began instead using the name Intel 64 for its implementation, paralleling AMD's use of the name AMD64.[30]
The first processor to implement Intel 64 was the multi-socket processor Xeon code-named Nocona in June 2004. In contrast, the initial Prescott chips (February 2004) did not enable this feature. Intel subsequently began selling Intel 64-enabled Pentium 4s using the E0 revision of the Prescott core, being sold on the OEM market as the Pentium 4, model F. The E0 revision also adds eXecute Disable (XD) (Intel's name for the NX bit) to Intel 64, and has been included in then current Xeon code-named Irwindale. Intel's official launch of Intel 64 (under the name EM64T at that time) in mainstream desktop processors was the N0 stepping Prescott-2M.
The first Intel mobile processor implementing Intel 64 is the Merom version of the Core 2 processor, which was released on July 27, 2006. None of Intel's earlier notebook CPUs (Core Duo, Pentium M, Celeron M, Mobile Pentium 4) implement Intel 64.
Implementations[edit]
Intel's processors implementing the Intel64 architecture include the Pentium 4 F-series/5x1 series, 506, and 516, Celeron D models 3x1, 3x6, 355, 347, 352, 360, and 365 and all later Celerons, all models of Xeon since "Nocona", all models of Pentium Dual-Core processors since "Merom-2M", the Atom 230, 330, D410, D425, D510, D525, N450, N455, N470, N475, N550, N570, N2600 and N2800, and all versions of the Pentium D, Pentium Extreme Edition, Core 2, Core i7, Core i5, and Core i3 processors.
VIA's x86-64 implementation[edit]
VIA Technologies introduced their first implementation of the x86-64 architecture in 2008 after five years of development by its CPU division, Centaur Technology.[31] Codenamed "Isaiah", the 64-bit architecture was unveiled on January 24, 2008,[32] and launched on May 29 under the VIA Nano brand name.[33]
The processor supports a number of VIA-specific x86 extensions designed to boost efficiency in low-power appliances. It is expected that the Isaiah architecture will be twice as fast in integer performance and four times as fast in floating-point performance as the previous-generation VIA Esther at an equivalent clock speed. Power consumption is also expected to be on par with the previous-generation VIA CPUs, with thermal design power ranging from 5 W to 25 W.[34] Being a completely new design, the Isaiah architecture was built with support for features like the x86-64 instruction set and x86 virtualization which were unavailable on its predecessors, the VIA C7 line, while retaining their encryption extensions.
Differences between AMD64 and Intel 64[edit]
Although nearly identical, there are some differences between the two instruction sets in the semantics of a few seldom used machine instructions (or situations), which are mainly used for system programming.[35] Compilers generally produce executables (i.e. machine code) that avoid any differences, at least for ordinary application programs. This is therefore of interest mainly to developers of compilers, operating systems and similar, which must deal with individual and special system instructions.
Recent implementations[edit]
Intel 64's BSF and BSR instructions act differently than AMD64's when the source is zero and the operand size is 32 bits. The processor sets the zero flag and leaves the upper 32 bits of the destination undefined.
AMD64 requires a different microcode update format and control MSRs (model-specific registers) while Intel 64 implements microcode update unchanged from their 32-bit only processors.
Intel 64 lacks some MSRs that are considered architectural in AMD64. These include SYSCFG, TOP_MEM, and TOP_MEM2.
Intel 64 allows SYSCALL/SYSRET only in 64-bit mode (not in compatibility mode),[36] and allows SYSENTER/SYSEXIT in both modes.[37] AMD64 lacks SYSENTER/SYSEXIT in both sub-modes of long mode.[11]:33
In 64-bit mode, near branches with the 66H (operand size override) prefix behave differently. Intel 64 ignores this prefix: the instruction has 32-bit sign extended offset, and instruction pointer is not truncated. AMD64 uses 16-bit offset field in the instruction, and clears the top 48 bits of instruction pointer.
AMD processors raise a floating point Invalid Exception when performing an FLD or FSTP of an 80-bit signalling NaN, while Intel processors do not.
Intel 64 lacks the ability to save and restore a reduced (and thus faster) version of the floating-point state (involving the FXSAVE and FXRSTOR instructions).
AMD processors ever since Opteron Rev. E and Athlon 64 Rev. D have reintroduced limited support for segmentation, via the Long Mode Segment Limit Enable (LMSLE) bit, to ease virtualization of 64-bit guests.[38][39]
When returning to a non-canonical address using SYSRET, AMD64 processors execute the general protection fault handler in privilege level 3,[40] while on Intel 64 processors it is executed in privilege level 0.[41]
Older implementations[edit]
Early AMD64 processors (typically on Socket 939 and 940) lacked the CMPXCHG16B instruction, which is an extension of the CMPXCHG8B instruction present on most post-80486 processors. Similar to CMPXCHG8B, CMPXCHG16B allows for atomic operations on octal words. This is useful for parallel algorithms that use compare and swap on data larger than the size of a pointer, common in lock-free and wait-free algorithms. Without CMPXCHG16B one must use workarounds, such as a critical section or alternative lock-free approaches.[42] Its absence also prevents 64-bit Windows prior to Windows 8.1 from having a user-mode address space larger than 8 terabytes.[43] The 64-bit version of Windows 8.1 requires the instruction.[44]
Early AMD64 and Intel 64 CPUs lacked LAHF and SAHF instructions in 64-bit mode. AMD introduced these instructions (also in 64-bit mode) with their Athlon 64, Opteron and Turion 64 revision D processors in March 2005[45][46][47] while Intel introduced the instructions with the Pentium 4 G1 stepping in December 2005. The 64-bit version of Windows 8.1 requires this feature.[44]
Early Intel CPUs with Intel 64 also lack the NX bit of the AMD64 architecture. This feature is required by all versions of Windows 8.x.
Early Intel 64 implementations (Prescott and Cedar Mill) only allowed access to 64 GB of physical memory while original AMD64 implementations allowed access to 1 TB of physical memory. Recent AMD64 implementations provide 256 TB of physical address space (and AMD plans an expansion to 4 PB),[citation needed] while some Intel 64 implementations could address up to 64 TB.[48] Physical memory capacities of this size are appropriate for large-scale applications (such as large databases), and high-performance computing (centrally oriented applications and scientific computing).
Adoption[edit]
An area chart showing the representation of different families of microprocessors in the TOP500 supercomputer ranking list, from 1992 to 2014.[49]
In supercomputers tracked by TOP500, the appearance of 64-bit extensions for the x86 architecture enabled 64-bit x86 processors by AMD and Intel (light olive with circles, and red with circles on the diagram provided in this section, respectively) to replace most RISC processor architectures previously used in such systems (including PA-RISC, SPARC, Alpha and others), as well as 32-bit x86 (green with dots and purple with dots on the diagram), even though Intel itself initially tried unsuccessfully to replace x86 with a new incompatible 64-bit architecture in the Itanium processor.
As of 2014[update], the main non-x86 CPU architecture which is still used in supercomputing is the Power Architecture used by IBM POWER microprocessors (blue with a diamond pattern on the diagram), with SPARC being far behind in numbers on TOP500, while recently a Fujitsu SPARC64 VIIIfx based supercomputer without co-processors reached number one that is still in the top ten. Non-CPU architecture co-processors (GPGPU) have also played a big role in performance. Intel's Xeon Phi coprocessors, which implement a subset of x86-64 with some vector extensions,[50] are also used, along with x86-64 processors, in the Tianhe-2 supercomputer.[51]
Operating system compatibility and characteristics[edit]
The following operating systems and releases support the x86-64 architecture in long mode.
BSD[edit]
DragonFly BSD[edit]
Preliminary infrastructure work was started in February 2004 for a x86-64 port.[52] This development later stalled. Development started again during July 2007[53] and continued during Google Summer of Code 2008 and SoC 2009.[54][55] The first official release to contain x86-64 support was version 2.4.[56]
FreeBSD[edit]
FreeBSD first added x86-64 support under the name "amd64" as an experimental architecture in 5.1-RELEASE in June 2003. It was included as a standard distribution architecture as of 5.2-RELEASE in January 2004. Since then, FreeBSD has designated it as a Tier 1 platform. The 6.0-RELEASE version cleaned up some quirks with running x86 executables under amd64, and most drivers work just as they do on the x86 architecture. Work is currently being done to integrate more fully the x86 application binary interface (ABI), in the same manner as the Linux 32-bit ABI compatibility currently works.
NetBSD[edit]
x86-64 architecture support was first committed to the NetBSD source tree on June 19, 2001. As of NetBSD 2.0, released on December 9, 2004, NetBSD/amd64 is a fully integrated and supported port. 32-bit code is still supported in 64-bit mode, with a netbsd-32 kernel compatibility layer for 32-bit syscalls. The NX bit is used to provide non-executable stack and heap with per-page granularity (segment granularity being used on 32-bit x86).
OpenBSD[edit]
OpenBSD has supported AMD64 since OpenBSD 3.5, released on May 1, 2004. Complete in-tree implementation of AMD64 support was achieved prior to the hardware's initial release because AMD had loaned several machines for the project's hackathon that year. OpenBSD developers have taken to the platform because of its support for the NX bit, which allowed for an easy implementation of the W^X feature.
The code for the AMD64 port of OpenBSD also runs on Intel 64 processors which contains cloned use of the AMD64 extensions, but since Intel left out the page table NX bit in early Intel 64 processors, there is no W^X capability on those Intel CPUs; later Intel 64 processors added the NX bit under the name "XD bit". Symmetric multiprocessing (SMP) works on OpenBSD's AMD64 port, starting with release 3.6 on November 1, 2004.
DOS[edit]
It is possible to enter long mode under DOS without a DOS extender,[57] but the user must return to real mode in order to call BIOS or DOS interrupts.
It may also be possible to enter long mode with a DOS extender similar to DOS/4GW, but more complex since x86-64 lacks virtual 8086 mode. DOS itself is not aware of that, and no benefits should be expected unless running DOS in an emulation with an adequate virtualization driver backend, for example: the mass storage interface.
Linux[edit]
See also: Comparison of Linux distributions § Instruction set architecture support
Linux was the first operating system kernel to run the x86-64 architecture in long mode, starting with the 2.4 version in 2001 (preceding the hardware's availability).[58][59] Linux also provides backward compatibility for running 32-bit executables. This permits programs to be recompiled into long mode while retaining the use of 32-bit programs. Several Linux distributions currently ship with x86-64-native kernels and userlands. Some, such as Arch Linux,[60] SUSE, Mandriva, and Debian allow users to install a set of 32-bit components and libraries when installing off a 64-bit DVD, thus allowing most existing 32-bit applications to run alongside the 64-bit OS. Other distributions, such as Fedora, Slackware and Ubuntu, are available in one version compiled for a 32-bit architecture and another compiled for a 64-bit architecture. Fedora and Red Hat Enterprise Linux allow concurrent installation of all userland components in both 32 and 64-bit versions on a 64-bit system.
x32 ABI (Application Binary Interface), introduced in Linux 3.4, allows programs compiled for the x32 ABI to run in the 64-bit mode of x86-64 while only using 32-bit pointers and data fields.[61][62][63] Though this limits the program to a virtual address space of 4 GB it also decreases the memory footprint of the program and in some cases can allow it to run faster.[61][62][63]
64-bit Linux allows up to 128 TB of virtual address space for individual processes, and can address approximately 64 TB of physical memory, subject to processor and system limitations.[64]
macOS[edit]
Mac OS X 10.4.7 and higher versions of Mac OS X 10.4 run 64-bit command-line tools using the POSIX and math libraries on 64-bit Intel-based machines, just as all versions of Mac OS X 10.4 and 10.5 run them on 64-bit PowerPC machines. No other libraries or frameworks work with 64-bit applications in Mac OS X 10.4.[65] The kernel, and all kernel extensions, are 32-bit only.
Mac OS X 10.5 supports 64-bit GUI applications using Cocoa, Quartz, OpenGL, and X11 on 64-bit Intel-based machines, as well as on 64-bit PowerPC machines.[66] All non-GUI libraries and frameworks also support 64-bit applications on those platforms. The kernel, and all kernel extensions, are 32-bit only.
Mac OS X 10.6 is the first version of macOS that supports a 64-bit kernel. However, not all 64-bit computers can run the 64-bit kernel, and not all 64-bit computers that can run the 64-bit kernel will do so by default.[67] The 64-bit kernel, like the 32-bit kernel, supports 32-bit applications; both kernels also support 64-bit applications. 32-bit applications have a virtual address space limit of 4 GB under either kernel.[68][69]
OS X 10.8 includes only the 64-bit kernel, but continues to support 32-bit applications.
The 64-bit kernel does not support 32-bit kernel extensions, and the 32-bit kernel does not support 64-bit kernel extensions.
macOS uses the universal binary format to package 32- and 64-bit versions of application and library code into a single file; the most appropriate version is automatically selected at load time. In Mac OS X 10.6, the universal binary format is also used for the kernel and for those kernel extensions that support both 32-bit and 64-bit kernels.
Solaris[edit]
See also: illumos
Solaris 10 and later releases support the x86-64 architecture.
For Solaris 10, just as with the SPARC architecture, there is only one operating system image, which contains a 32-bit kernel and a 64-bit kernel; this is labeled as the "x64/x86" DVD-ROM image. The default behavior is to boot a 64-bit kernel, allowing both 64-bit and existing or new 32-bit executables to be run. A 32-bit kernel can also be manually selected, in which case only 32-bit executables will run. The isainfo command can be used to determine if a system is running a 64-bit kernel.
For Solaris 11, only the 64-bit kernel is provided. However, the 64-bit kernel supports both 32- and 64-bit executables, libraries, and system calls.
Windows[edit]
x64 editions of Microsoft Windows client and server—Windows XP Professional x64 Edition and Windows Server 2003 x64 Edition—were released in March 2005.[70] Internally they are actually the same build (5.2.3790.1830 SP1),[71][72] as they share the same source base and operating system binaries, so even system updates are released in unified packages, much in the manner as Windows 2000 Professional and Server editions for x86. Windows Vista, which also has many different editions, was released in January 2007. Windows 7 was released in July 2009. Windows Server 2008 R2 was sold in only x64 and Itanium editions; later versions of Windows Server only offer an x64 edition.
Versions of Windows for x64 prior to Windows 8.1 and Windows Server 2012 R2 offer the following:
8 TB of virtual address space per process, accessible from both user mode and kernel mode, referred to as the user mode address space. An x64 program can use all of this, subject to backing store limits on the system, and provided it is linked with the "large address aware" option.[73] This is a 4096-fold increase over the default 2 GB user-mode virtual address space offered by 32-bit Windows.[74][75]
8 TB of kernel mode virtual address space for the operating system.[74] As with the user mode address space, this is a 4096-fold increase over 32-bit Windows versions. The increased space primarily benefits the file system cache and kernel mode "heaps" (non-paged pool and paged pool). Windows only uses a total of 16 TB out of the 256 TB implemented by the processors because early AMD64 processors lacked a CMPXCHG16B instruction.[76]
Under Windows 8.1 and Windows Server 2012 R2, both user mode and kernel mode virtual address spaces have been extended to 128 TB.[21] These versions of Windows will not install on processors that lack the CMPXCHG16B instruction.
The following additional characteristics apply to all x64 versions of Windows:
Ability to run existing 32-bit applications (.exe programs) and dynamic link libraries (.dlls) using WoW64 if WoW64 is supported on that version. Furthermore, a 32-bit program, if it was linked with the "large address aware" option,[73] can use up to 4 GB of virtual address space in 64-bit Windows, instead of the default 2 GB (optional 3 GB with /3GB boot option and "large address aware" link option) offered by 32-bit Windows.[77] Unlike the use of the /3GB boot option on x86, this does not reduce the kernel mode virtual address space available to the operating system. 32-bit applications can therefore benefit from running on x64 Windows even if they are not recompiled for x86-64.
Both 32- and 64-bit applications, if not linked with "large address aware," are limited to 2 GB of virtual address space.
Ability to use up to 128 GB (Windows XP/Vista), 192 GB (Windows 7), 512 GB (Windows 8), 1 TB (Windows Server 2003), 2 TB (Windows Server 2008/Windows 10), 4 TB (Windows Server 2012), or 24 TB (Windows Server 2016) of physical random access memory (RAM).[78]
LLP64 data model: "int" and "long" types are 32 bits wide, long long is 64 bits, while pointers and types derived from pointers are 64 bits wide.
Kernel mode device drivers must be 64-bit versions; there is no way to run 32-bit kernel mode executables within the 64-bit operating system. User mode device drivers can be either 32-bit or 64-bit.
16-bit Windows (Win16) and DOS applications will not run on x86-64 versions of Windows due to removal of the virtual DOS machine subsystem (NTVDM) which relied upon the ability to use virtual 8086 mode. Virtual 8086 mode cannot be entered while running in long mode.
Full implementation of the NX (No Execute) page protection feature. This is also implemented on recent 32-bit versions of Windows when they are started in PAE mode.
Instead of FS segment descriptor on x86 versions of the Windows NT family, GS segment descriptor is used to point to two operating system defined structures: Thread Information Block (NT_TIB) in user mode and Processor Control Region (KPCR) in kernel mode. Thus, for example, in user mode GS:0 is the address of the first member of the Thread Information Block. Maintaining this convention made the x86-64 port easier, but required AMD to retain the function of the FS and GS segments in long mode – even though segmented addressing per se is not really used by any modern operating system.[74]
Early reports claimed that the operating system scheduler would not save and restore the x87 FPU machine state across thread context switches. Observed behavior shows that this is not the case: the x87 state is saved and restored, except for kernel mode-only threads (a limitation that exists in the 32-bit version as well). The most recent documentation available from Microsoft states that the x87/MMX/3DNow! instructions may be used in long mode, but that they are deprecated and may cause compatibility problems in the future.[77]
Some components like Microsoft Jet Database Engine and Data Access Objects will not be ported to 64-bit architectures such as x86-64 and IA-64.[79][80]
Microsoft Visual Studio can compile native applications to target either the x86-64 architecture, which can run only on 64-bit Microsoft Windows, or the IA-32 architecture, which can run as a 32-bit application on 32-bit Microsoft Windows or 64-bit Microsoft Windows in WoW64 emulation mode. Managed applications can be compiled either in IA-32, x86-64 or AnyCPU modes. Software created in the first two modes behave like their IA-32 or x86-64 native code counterparts respectively; When using the AnyCPU mode however, applications in 32-bit versions of Microsoft Windows run as 32-bit applications, while they run as a 64-bit application in 64-bit editions of Microsoft Windows.
Video game consoles[edit]
Both PlayStation 4 and Xbox One and their successors incorporate AMD x86-64 processors, based on the Jaguar microarchitecture.[81][82] Firmware and games are written in x86-64 code; no legacy x86 code is involved.
Industry naming conventions[edit]
Since AMD64 and Intel 64 are substantially similar, many software and hardware products use one vendor-neutral term to indicate their compatibility with both implementations. AMD's original designation for this processor architecture, "x86-64", is still sometimes used for this purpose,[2] as is the variant "x86_64".[3][4] Other companies, such as Microsoft[6] and Sun Microsystems/Oracle Corporation,[5] use the contraction "x64" in marketing material.
The term IA-64 refers to the Itanium processor, and should not be confused with x86-64, as it is a completely different instruction set.
Many operating systems and products, especially those that introduced x86-64 support prior to Intel's entry into the market, use the term "AMD64" or "amd64" to refer to both AMD64 and Intel 64.
amd64
Most BSD systems such as FreeBSD, MidnightBSD, NetBSD and OpenBSD refer to both AMD64 and Intel 64 under the architecture name "amd64".
Some Linux distributions such as Debian, Ubuntu, Gentoo Linux refer to both AMD64 and Intel 64 under the architecture name "amd64".
Microsoft Windows's x64 versions use the AMD64 moniker internally to designate various components which use or are compatible with this architecture. For example, the environment variable PROCESSOR_ARCHITECTURE is assigned the value "AMD64" as opposed to "x86" in 32-bit versions, and the system directory on a Windows x64 Edition installation CD-ROM is named "AMD64", in contrast to "i386" in 32-bit versions.[83]
Sun's Solaris' isalist command identifies both AMD64- and Intel 64-based systems as "amd64".
Java Development Kit (JDK): the name "amd64" is used in directory names containing x86-64 files.
x86_64
The Linux kernel[84] and the GNU Compiler Collection refers to 64-bit architecture as "x86_64".
Some Linux distributions, such as Fedora, openSUSE, Arch Linux, Gentoo Linux refer to this 64-bit architecture as "x86_64".
Apple macOS refers to 64-bit architecture as "x86-64" or "x86_64", as seen in the Terminal command arch[3] and in their developer documentation.[2][4]
Breaking with most other BSD systems, DragonFly BSD refers to 64-bit architecture as "x86_64".
Haiku refers to 64-bit architecture as "x86_64".
Licensing[edit]
x86-64/AMD64 was solely developed by AMD. AMD holds patents on techniques used in AMD64;[85][86][87] those patents must be licensed from AMD in order to implement AMD64. Intel entered into a cross-licensing agreement with AMD, licensing to AMD their patents on existing x86 techniques, and licensing from AMD their patents on techniques used in x86-64.[88] In 2009, AMD and Intel settled several lawsuits and cross-licensing disagreements, extending their cross-licensing agreements.[89][90][91]
See also[edit]
AMD Generic Encapsulated Software Architecture (AGESA)
X32 ABI
Notes[edit]
Jump up ^ Various names are used for the instruction set. Prior to the launch, x86-64 and x86_64 were used, while upon the release AMD named it AMD64.[1] Intel initially used the names IA-32e and EM64T before finally settling on "Intel 64" for its implementation. Some in the industry, including Apple,[2][3][4] use x86-64 and x86_64, while others, notably Sun Microsystems[5] (now Oracle Corporation) and Microsoft,[6] use x64. The BSD family of OSs and several Linux distributions[7][8] use AMD64, as does Microsoft Windows internally.[9][10]
Jump up ^ In practice, 64-bit operating systems generally do not support 16-bit applications, although modern versions of Microsoft Windows contain a limited workaround that effectively supports 16-bit InstallShield and Microsoft ACME installers by silently substituting them with 32-bit code.[12]
References[edit]
Jump up ^ "Debian AMD64 FAQ". Debian Wiki. Retrieved 2012-05-03.
^ Jump up to: a b c "x86-64 Code Model". Apple. Retrieved November 23, 2012.
^ Jump up to: a b c arch(1) – Darwin and macOS General Commands Manual
^ Jump up to: a b c Kevin Van Vechten (2006-08-09). "re: Intel XNU bug report". Darwin-dev mailing list. Apple Computer. Retrieved 2006-10-05. The kernel and developer tools have standardized on "x86_64" for the name of the Mach-O architecture
^ Jump up to: a b "Solaris 10 on AMD Opteron". Oracle. Retrieved 2010-12-09.
^ Jump up to: a b "Microsoft 64-Bit Computing". Microsoft. Retrieved 2010-12-09.
Jump up ^ "AMD64 Port". Debian. Retrieved November 23, 2012.
Jump up ^ "Gentoo/AMD64 Project". Gentoo Project. Retrieved May 27, 2013.
Jump up ^ "WOW64 Implementation Details".
Jump up ^ "ProcessorArchitecture Class".
^ Jump up to: a b c d e f g h i j k l m n o p q r AMD Corporation (December 2016). "Volume 2: System Programming" (PDF). AMD64 Architecture Programmer's Manual. AMD Corporation. Retrieved 2017-03-25.
Jump up ^ Raymond Chen (October 31, 2013). "If there is no 16-bit emulation layer in 64-bit Windows, how come certain 16-bit installers are allowed to run?".
Jump up ^ IBM Corporation (2007-09-06). "IBM WebSphere Application Server 64-bit Performance Demystified" (PDF). p. 14. Retrieved 2010-04-09. Figures 5, 6 and 7 also show the 32-bit version of WAS runs applications at full native hardware performance on the POWER and x86-64 platforms. Unlike some 64-bit processor architectures, the POWER and x86-64 hardware does not emulate 32-bit mode. Therefore applications that do not benefit from 64-bit features can run with full performance on the 32-bit version of WebSphere running on the above mentioned 64-bit platforms.
Jump up ^ "AMD Discloses New Technologies At Microporcessor Forum" (Press release). AMD. 1999-10-05. Archived from the original on 2012-03-08. Retrieved 2010-11-09.
Jump up ^ "AMD Releases x86-64 Architectural Specification; Enables Market Driven Migration to 64-Bit Computing" (Press release). AMD. 2000-08-10. Archived from the original on 2012-03-08. Retrieved 2010-11-09.
Jump up ^ "Intel 64 and IA-32 Architectures Software Developer's Manual, Volume 3A: System Programming Guide, Part 1" (PDF). pp. 4–10. Retrieved 2010-05-29.
^ Jump up to: a b "BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors" (PDF). p. 24. Retrieved 2016-02-27. Physical address space increased to 48 bits.
Jump up ^ "Myth and facts about 64-bit Linux" (PDF). March 2, 2008. p. 7. Archived from the original (PDF) on October 10, 2010. Retrieved May 30, 2010. Physical address space increased to 48 bits
Jump up ^ Shanley, Tom (1998). Pentium Pro and Pentium II System Architecture. PC System Architecture Series (Second ed.). Addison-Wesley. p. 445. ISBN 0-201-30973-4.
Jump up ^ Microsoft Corporation. "What is PAE, NX, and SSE2 and why does my PC need to support them to run Windows 8 ?". Retrieved 19 March 2013.
^ Jump up to: a b c d "Memory Limits for Windows Releases". MSDN. Microsoft. November 16, 2013. Retrieved January 20, 2014.
Jump up ^ "5-Level Paging and 5-Level EPT" (PDF). Intel. May 2017. Retrieved June 17, 2017.
Jump up ^ "Opteron 6100 Series Motherboards". Supermicro Corporation. Retrieved 2010-06-22.
Jump up ^ "Supermicro XeonSolutions". Supermicro Corporation. Retrieved 2010-06-20.
Jump up ^ "Opteron 8000 Series Motherboards". Supermicro Corporation. Retrieved 2010-06-20.
Jump up ^ "Tyan Product Matrix". MiTEC International Corporation. Retrieved 2010-06-21.
Jump up ^ "Craig Barrett confirms 64 bit address extensions for Xeon. And Prescott". The Inquirer. 2004-02-17.
Jump up ^ "A Roundup of 64-Bit Computing", from internetnews.com
Jump up ^ "Intel 64 Architecture". Intel. Retrieved 2007-06-29.
Jump up ^ "VIA to launch new processor architecture in 1Q08" (subscription required). DigiTimes. Retrieved 2007-07-25.
Jump up ^ Stokes, Jon (2008-01-23). "Isaiah revealed: VIA's new low-power architecture". Ars Technica. Retrieved 2008-01-24.
Jump up ^ "VIA Launches VIA Nano Processor Family" (Press release). VIA. 2008-05-29. Retrieved 2017-05-25.
Jump up ^ "VIA Isaiah Architecture Introduction" (PDF). VIA. January 23, 2008. Archived from the original (PDF) on September 7, 2008. Retrieved July 31, 2013.
Jump up ^ Wasson, Scott. "64-bit computing in theory and practice". The Tech Report. The Tech Report. Retrieved 2011-03-22.
Jump up ^ "Intel 64 and IA-32 Architectures Software Developer's Manual Volume 2 (2A, 2B & 2C): Instruction Set Reference, A-Z" (PDF). Intel. September 2013. pp. 4–397. Retrieved 2014-01-21.
Jump up ^ "Intel 64 and IA-32 Architectures Software Developer's Manual Volume 2 (2A, 2B & 2C): Instruction Set Reference, A-Z" (PDF). Intel. September 2013. pp. 4–400. Retrieved 2014-01-21.
Jump up ^ "How retiring segmentation in AMD64 long mode broke VMware". Pagetable.com. 2006-11-09. Retrieved 2010-05-02.
Jump up ^ "VMware and CPU Virtualization Technology" (PDF). VMWare. Retrieved 2010-09-08.
Jump up ^ "AMD64 Architecture Programmer's Manual Volume 3: General-Purpose and System Instructions" (PDF). AMD. May 2018. p. 419. Retrieved 2018-08-02.
Jump up ^ "Intel 64 and IA-32 Architectures Software Developer's Manual Volume 2 (2A, 2B & 2C): Instruction Set Reference, A-Z" (PDF). Intel. September 2014. pp. 4–412. Retrieved 2014-12-28.
Jump up ^ Maged M. Michael. "Practical Lock-Free and Wait-Free LL/SC/VL Implementations Using 64-Bit CAS" (PDF). IBM. Retrieved 2014-01-21.
Jump up ^ darwou (August 20, 2004). "Why is the virtual address space 4GB anyway?". The Old New Thing. Microsoft.
^ Jump up to: a b "System Requirements—Windows 8.1". Retrieved 2014-04-27. To install a 64-bit OS on a 64-bit PC, your processor needs to support CMPXCHG16b, PrefetchW, and LAHF/SAHF.
Jump up ^ "Revision Guide for AMD Athlon 64 and AMD Opteron Processors", from AMD
Jump up ^ "AMD Turion 64 pictured up and running", from The Inquirer
Jump up ^ "Athlon 64 revision E won't work on some Nforce 3/4 boards", from The Inquirer
Jump up ^ "Intel 64 architecture increases the linear address space for software to 64 bits and supports physical address space up to 46 bits." on page Vol. 1 2-21 of Intel 64 and IA-32 Architectures Software Developer’s Manual September 2014
Jump up ^ "Statistics | TOP500 Supercomputer Sites". Top500.org. Retrieved 2014-03-22.
Jump up ^ "Intel® Xeon PhiTM Coprocessor Instruction Set Architecture Reference Manual" (PDF). Intel. September 7, 2012. section B.2 Intel Xeon Phi coprocessor 64 bit Mode Limitations.
Jump up ^ "Intel Powers the World's Fastest Supercomputer, Reveals New and Future High Performance Computing Technologies". Retrieved June 21, 2013.
Jump up ^ "cvs commit: src/sys/amd64/amd64 genassym.c src/sys/amd64/include asm.h atomic.h bootinfo.h coredump.h cpufunc.h elf.h endian.h exec.h float.h fpu.h frame.h globaldata.h ieeefp.h limits.h lock.h md_var.h param.h pcb.h pcb_ext.h pmap.h proc.h profile.h psl.h ..." Retrieved 2009-05-03.
Jump up ^ "AMD64 port". Retrieved 2009-05-03.
Jump up ^ "DragonFlyBSD: GoogleSoC2008". Retrieved 2009-05-03.
Jump up ^ "Summer of Code accepted students". Retrieved 2009-05-03.
Jump up ^ "DragonFlyBSD: release24". Retrieved 2009-05-03.
Jump up ^ Tutorial for entering protected and long mode from DOS
Jump up ^ Andi Kleen (June 26, 2001). "Porting Linux to x86-64". Archived from the original on September 10, 2010. Status: The kernel, compiler, tool chain work. The kernel boots and work on simulator and is used for porting of userland and running programs
Jump up ^ Andi Kleen. "Andi Kleen's Page". This was the original paper describing the Linux x86-64 kernel port back when x86-64 was only available on simulators.
Jump up ^ "Arch64 FAQ". 2012-04-23. You can either use the multilib packages or a i686 chroot.
^ Jump up to: a b Thorsten Leemhuis (September 13, 2011). "Kernel Log: x32 ABI gets around 64-bit drawbacks". www.h-online.com. Archived from the original on October 28, 2011. Retrieved November 1, 2011.
^ Jump up to: a b "x32 - a native 32-bit ABI for x86-64". linuxplumbersconf.org. Retrieved 2011-11-01.
^ Jump up to: a b "x32-abi". Google Sites. Retrieved 2011-11-01.
Jump up ^ "AMD64 Port". debian.org. Retrieved 2011-10-29.
Jump up ^ "Apple – Mac OS X Xcode 2.4 Release Notes: Compiler Tools". Apple Inc. 2007-04-11. Archived from the original on 2009-04-22. Retrieved 2012-11-19.
Jump up ^ "Apple – Mac OS X Leopard – Technology - 64-bit". Apple Inc. Archived from the original on 2009-01-12. Retrieved 2012-11-19.
Jump up ^ "Mac OS X v10.6: Macs that use the 64-bit kernel". Apple Inc. Retrieved 2012-11-29.
Jump up ^ John Siracusa. "Mac OS X 10.6 Snow Leopard: the Ars Technica review". Ars Technica LLC. Retrieved 2010-06-20.
Jump up ^ "Mac OS X Technology". Apple Inc. Archived from the original on 2011-03-28. Retrieved 2012-11-19.
Jump up ^ "Microsoft Raises the Speed Limit with the Availability of 64-Bit Editions of Windows Server 2003 and Windows XP Professional | News Center". news.microsoft.com. Retrieved 2016-08-14.
Jump up ^ "A description of the x64-based versions of Windows Server 2003 and of Windows XP Professional x64 Edition". Microsoft Support. Retrieved 2016-08-14.
Jump up ^ "Windows Server 2003 SP1 Administration Tools Pack". Microsoft Download Center. Retrieved 2016-08-14.
^ Jump up to: a b "/LARGEADDRESSAWARE (Handle Large Addresses)". Visual Studio 2005 Documentation – Visual C++ – Linker Options. Microsoft. Retrieved 2010-06-19. The /LARGEADDRESSAWARE option tells the linker that the application can handle addresses larger than 2 gigabytes.
^ Jump up to: a b c Matt Pietrek (May 2006). "Everything You Need To Know To Start Programming 64-Bit Windows Systems". Microsoft. Retrieved 2010-05-24.
Jump up ^ Chris St. Amand (January 2006). "Making the Move to x64". Microsoft. Retrieved 2010-05-24.
Jump up ^ "Behind Windows x86-64's 44-bit Virtual Memory Addressing Limit". Retrieved 2009-07-02.
^ Jump up to: a b "64-bit programming for Game Developers". Retrieved August 21, 2013.
Jump up ^ "Memory Limits for Windows Releases". Microsoft. Retrieved February 20, 2013.
Jump up ^ Microsoft Developer Network – General Porting Guidelines (64-bit Windows Programming)
Jump up ^ Microsoft Developer Network – Data Access Road Map[permanent dead link]
Jump up ^ Anand Lal Shimpi (2013-05-21). "The Xbox One: Hardware Analysis & Comparison to PlayStation 4". Anandtech. Retrieved 2013-05-22.
Jump up ^ "The Tech Spec Test: Xbox One Vs. PlayStation 4". Game Informer. 2013-05-21. Retrieved 2013-05-22.
Jump up ^ ProcessorArchitecture Fields
Jump up ^ "An example file from Linux 3.7.8 kernel source tree displaying the usage of the term x86_64". Archived from the original on September 23, 2005. Retrieved February 17, 2013.
Jump up ^ US 6877084
Jump up ^ US 6889312
Jump up ^ US 6732258
Jump up ^ "Patent Cross License Agreement Between AMD and Intel". 2001-01-01. Archived from the original on June 21, 2007. Retrieved 2009-08-23.
Jump up ^ "AMD Intel Settlement Agreement".
Jump up ^ Stephen Shankland and Jonathan E. Skillings (2009-11-12). "Intel to pay AMD $1.25 billion in antitrust settlement". CNET. Retrieved 2012-04-24.
Jump up ^ Smith, Ryan (12 November 2009). "AMD and Intel Settle Their Differences: AMD Gets To Go Fabless". AnandTech. Archived from the original on 13 May 2010.
External links[edit]
AMD's AMD64 Developer Guides and Manuals
x86-64: Extending the x86 architecture to 64-bits – technical talk by the architect of AMD64 (video archive), and second talk by the same speaker (video archive)
AMD's "Enhanced Virus Protection"
Intel tweaks EM64T for full AMD64 compatibility
Analyst: Intel Reverse-Engineered AMD64
Early report of differences between Intel IA32e and AMD64
Porting to 64-bit GNU/Linux Systems, by Andreas Jaeger from GCC Summit 2003. An excellent paper explaining almost all practical aspects for a transition from 32-bit to 64-bit.
Tech Report article: 64-bit computing in theory and practice
Intel 64 Architecture
Intel Software Network: "64 bits"
TurboIRC.COM tutorial of entering the protected and the long mode the raw way from DOS
Seven Steps of Migrating a Program to a 64-bit System
Memory Limits for Windows Releases
Retrieved from "https://en.wikipedia.org/w/index.php?title=X86-64&oldid=856290783"
Categories:
Computer-related introductions in 2003
X86 architecture
Hidden categories:
All articles with dead external links
Articles with dead external links from July 2016
Articles with permanently dead external links
Use mdy dates from May 2014
Articles containing potentially dated statements from June 2010
All articles containing potentially dated statements
All articles with failed verification
Articles with failed verification from May 2016
All articles with unsourced statements
Articles with unsourced statements from August 2017
All articles that may contain original research
Articles that may contain original research from August 2017
Articles with unsourced statements from October 2010
Articles containing potentially dated statements from 2014
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
العربية
Български
Čeština
Dansk
Deutsch
Eesti
Ελληνικά
Español
فارسی
Français
한국어
עברית
Magyar
Bahasa Melayu
Nederlands
日本語
Norsk
Polski
Română
Русский
Scots
Simple English
Slovenčina
Slovenščina
Српски / srpski
Svenska
ไทย
Türkçe
Tiếng Việt
粵語
中文
22 more
Edit links
This page was last edited on 24 August 2018, at 05:24 (UTC).
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

key: html

type: local

value: div

attrs: id class

values: mw-page-base noprint

values: mw-head-base noprint

value: a

attrs: id class lang

values: firstHeading firstHeading en

values: siteSub noprint

attrs: class href

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

attrs: href title

attrs: role class

values:
note
hatnote navigation-not-searchable

value: span

value: p

value: img

attrs: alt src width height class srcset data-file-width data-file-height

attrs: href class

attrs: href class title

attrs: class style

values:
/wiki/Instruction_set
mw-redirect
Instruction set

values:
/wiki/Physical_memory
mw-redirect
Physical memory

values:
/wiki/General-purpose_register
mw-redirect
General-purpose register

values:
/wiki/Intel_Corporation
mw-redirect
Intel Corporation

values: checkbox button toctogglecheckbox toctogglecheckbox display:none

values:
/wiki/Hewlett_Packard
mw-redirect
Hewlett Packard

values:
/wiki/Athlon_64_FX
mw-redirect
Athlon 64 FX

values:
/wiki/Turion_64_X2
mw-redirect
Turion 64 X2

values:
/wiki/Phenom_(processor)
mw-redirect
Phenom (processor)

values:
/wiki/Protected_Virtual_Address_Mode
mw-redirect
Protected Virtual Address Mode

values:
/wiki/Stack_(data_structure)
mw-redirect
Stack (data structure)

values:
/wiki/Position_independent_code
mw-redirect
Position independent code

values:
/wiki/Task_State_Segment
mw-redirect
Task State Segment

values: Edit section: Virtual address space details

attrs: alt src width height srcset data-file-width data-file-height

values:
/wiki/Kernel_space
mw-redirect
Kernel space

values: Edit section: Physical address space details

values: plainlinks noexcerpt noprint asof-tag update

values: The material near this tag failed verification of its source citation(s). (May 2016)

values:
reflist mw-references-wrap
list-style-type: decimal;

values: This claim needs references to reliable sources. (August 2017)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values: The material near this tag possibly contains original research. (August 2017)

values:
/wiki/Pentium_Extreme_Edition
mw-redirect
Pentium Extreme Edition

values:
/wiki/Intel_Core_i7
mw-redirect
Intel Core i7

values:
/wiki/Intel_Core_i5
mw-redirect
Intel Core i5

values: Edit section: VIA's x86-64 implementation

values:
/wiki/Clock_speed
mw-redirect
Clock speed

values: Edit section: Differences between AMD64 and Intel 64

values:
/wiki/Atomic_operation
mw-redirect
Atomic operation

values:
/wiki/Compare_and_swap
mw-redirect
Compare and swap

values: This claim needs references to reliable sources. (October 2010)

values:
/wiki/SPARC64_VIIIfx
mw-redirect
SPARC64 VIIIfx

values: General-purpose computing on graphics processing units

values: Edit section: Operating system compatibility and characteristics

values:
/wiki/Userland_(computing)
mw-redirect
Userland (computing)

values:
/wiki/Kernel_(computing)
mw-redirect
Kernel (computing)

values:
/wiki/Data_Access_Objects
mw-redirect
Data Access Objects

values:
/wiki/Native_code
mw-redirect
Native code

values: Edit section: Industry naming conventions

values: AMD Generic Encapsulated Software Architecture

values:
nofollow
external text
http://wiki.debian.org/DebianAMD64Faq

values:
/wiki/Apple_Computer
mw-redirect
Apple Computer

values:
nofollow
http://www.debian.org/ports/amd64/
external text

values:
nofollow
external text
http://techreport.com/articles.x/8131/1

values:
nofollow
external text
http://www.pagetable.com/?p=25

values:
nofollow
external text
http://www.top500.org/statistics

values:
nofollow
http://www.dragonflybsd.org/release24/
external text

values:
nofollow
external text
http://www.turboirc.com/asm

values:
nofollow
http://www.halobates.de/
external text

values:
nofollow
http://sites.google.com/site/x32abi/
external text

values:
nofollow
external text
http://support.apple.com/kb/HT3770

values:
nofollow
external text
http://www.alex-ionescu.com/?p=50

values:
nofollow
external text
http://www.anandtech.com/show/2873

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values: Category:Computer-related introductions in 2003

values: Category:All articles with dead external links

values: Category:Articles with dead external links from July 2016

values: Category:Articles with permanently dead external links

values: Category:Articles containing potentially dated statements from June 2010

values: Category:All articles containing potentially dated statements

values: Category:All articles with failed verification

values: Category:Articles with failed verification from May 2016

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from August 2017

values: Category:All articles that may contain original research

values: Category:Articles that may contain original research from August 2017

values: Category:Articles with unsourced statements from October 2010

values: Category:Articles containing potentially dated statements from 2014

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/X86-64
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values:
/w/index.php?title=X86-64&action=edit
Edit this page [ctrl-alt-e]
e

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values:
https://bg.wikipedia.org/wiki/X86-64
X86-64 – Bulgarian
bg
bg
interlanguage-link-target

values:
interlanguage-link interwiki-bg
display: none;

values:
https://cs.wikipedia.org/wiki/X86-64
X86-64 – Czech
cs
cs
interlanguage-link-target

values:
interlanguage-link interwiki-cs
display: none;

values:
https://da.wikipedia.org/wiki/X86-64
X86-64 – Danish
da
da
interlanguage-link-target

values:
interlanguage-link interwiki-da
display: none;

values:
https://de.wikipedia.org/wiki/X64
X64 – German
de
de
interlanguage-link-target

values:
https://et.wikipedia.org/wiki/X86-64
X86-64 – Estonian
et
et
interlanguage-link-target

values:
interlanguage-link interwiki-et
display: none;

values:
https://el.wikipedia.org/wiki/X86-64
X86-64 – Greek
el
el
interlanguage-link-target

values:
interlanguage-link interwiki-el
display: none;

values:
https://es.wikipedia.org/wiki/X86-64
X86-64 – Spanish
es
es
interlanguage-link-target

values:
https://fa.wikipedia.org/wiki/X86-64
X86-64 – Persian
fa
fa
interlanguage-link-target

values:
interlanguage-link interwiki-fa
display: none;

values:
https://fr.wikipedia.org/wiki/X64
X64 – French
fr
fr
interlanguage-link-target

values:
https://ko.wikipedia.org/wiki/X86-64
X86-64 – Korean
ko
ko
interlanguage-link-target

values:
https://he.wikipedia.org/wiki/X86-64
X86-64 – Hebrew
he
he
interlanguage-link-target

values:
interlanguage-link interwiki-he
display: none;

values:
https://hu.wikipedia.org/wiki/X86-64
X86-64 – Hungarian
hu
hu
interlanguage-link-target

values:
interlanguage-link interwiki-hu
display: none;

values:
https://ms.wikipedia.org/wiki/X86-64
X86-64 – Malay
ms
ms
interlanguage-link-target

values:
https://nl.wikipedia.org/wiki/X86-64
X86-64 – Dutch
nl
nl
interlanguage-link-target

values:
interlanguage-link interwiki-nl
display: none;

values:
https://ja.wikipedia.org/wiki/X64
X64 – Japanese
ja
ja
interlanguage-link-target

values:
https://no.wikipedia.org/wiki/X86-64
X86-64 – Norwegian
no
no
interlanguage-link-target

values:
interlanguage-link interwiki-no
display: none;

values:
https://pl.wikipedia.org/wiki/X86-64
X86-64 – Polish
pl
pl
interlanguage-link-target

values:
interlanguage-link interwiki-pl
display: none;

values:
https://ro.wikipedia.org/wiki/X86-64
X86-64 – Romanian
ro
ro
interlanguage-link-target

values:
interlanguage-link interwiki-ro
display: none;

values:
https://ru.wikipedia.org/wiki/X86-64
X86-64 – Russian
ru
ru
interlanguage-link-target

values:
https://sco.wikipedia.org/wiki/X86-64
X86-64 – Scots
sco
sco
interlanguage-link-target

values:
interlanguage-link interwiki-sco
display: none;

values:
https://simple.wikipedia.org/wiki/X64
X64 – Simple English
simple
simple
interlanguage-link-target

values:
interlanguage-link interwiki-simple
display: none;

values:
https://sk.wikipedia.org/wiki/X86-64
X86-64 – Slovak
sk
sk
interlanguage-link-target

values:
interlanguage-link interwiki-sk
display: none;

values:
https://sl.wikipedia.org/wiki/X86-64
X86-64 – Slovenian
sl
sl
interlanguage-link-target

values:
interlanguage-link interwiki-sl
display: none;

values:
https://sr.wikipedia.org/wiki/X86-64
X86-64 – Serbian
sr
sr
interlanguage-link-target

values:
interlanguage-link interwiki-sr
display: none;

values:
https://sv.wikipedia.org/wiki/AMD64
AMD64 – Swedish
sv
sv
interlanguage-link-target

values:
interlanguage-link interwiki-sv
display: none;

values:
interlanguage-link interwiki-th
display: none;

values:
https://tr.wikipedia.org/wiki/X86-64
X86-64 – Turkish
tr
tr
interlanguage-link-target

values:
interlanguage-link interwiki-tr
display: none;

values:
https://vi.wikipedia.org/wiki/X86-64
X86-64 – Vietnamese
vi
vi
interlanguage-link-target

values:
interlanguage-link interwiki-vi
display: none;

values:
interlanguage-link interwiki-zh-yue
display: none;

values:
https://zh.wikipedia.org/wiki/X86-64
X86-64 – Chinese
zh
zh
interlanguage-link-target

values: All languages (initial selection from common choices by you and others)

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-X86-64 rootpage-X86-64 skin-vector action-view


text:
List of Billboard Hot 100 number-one singles of 1984
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
These are the Billboard Hot 100 number one hits of 1984. "Jump" by Van Halen and "When Doves Cry" by Prince each totaled five weeks at number one, the most of any song within 1984. However, "Like a Virgin" by Madonna had the longest run at number one of any song which rose into the top position during 1984. Though it spent only two weeks at number one at the end of the year, it went on to spend an additional four weeks at the top to begin 1985, for a total of six weeks. Overall, Prince spent the most weeks at number one in 1984, reigning for seven weeks at the top with "When Doves Cry" and "Let's Go Crazy" (with the Revolution).
Contents
[hide]
1 Chart history
2 See also
3 References
4 Additional sources
Chart history[edit]
Singer-songwriter/multi-instrumentalist Prince scored two number one singles with "When Doves Cry" and "Let's Go Crazy" with the Revolution. Overall, Prince spent seven weeks in the chart. Additionally, "When Doves Cry" tied with "Jump" by Van Halen as the longest-running number-one single of 1984, staying for five weeks at the top.
American hard rock band Van Halen gained their first and only number-one single in the chart with "Jump", which spent five weeks in the chart.
Singer Tina Turner gained her first and only U.S. number-one single with "What's Love Got to Do with It". Turner was 44 when the song spent three weeks at the top, at the time making her the oldest female solo artist to top the US Hot 100.
Key
The yellow background indicates the #1 song on Billboard's 1984 Year-End Chart of Pop Singles.
Issue Date
Song
Artist(s)
Reference
January 7 "Say Say Say" Paul McCartney and Michael Jackson [1]
January 14 [2]
January 21 "Owner of a Lonely Heart" Yes [3]
January 28 [4]
February 4 "Karma Chameleon" Culture Club [5]
February 11 [6]
February 18 [7]
February 25 "Jump" Van Halen [8]
March 3 [9]
March 10 [10]
March 17 [11]
March 24 [12]
March 31 "Footloose" Kenny Loggins [13]
April 7 [14]
April 14 [15]
April 21 "Against All Odds (Take a Look at Me Now)" Phil Collins [16]
April 28 [17]
May 5 [18]
May 12 "Hello" Lionel Richie [19]
May 19 [20]
May 26 "Let's Hear It for the Boy" Deniece Williams [21]
June 2 [22]
June 9 "Time After Time" Cyndi Lauper [23]
June 16 [24]
June 23 "The Reflex" Duran Duran [25]
June 30 [26]
July 7 "When Doves Cry" Prince [27]
July 14 [28]
July 21 [29]
July 28 [30]
August 4 [31]
August 11 "Ghostbusters" Ray Parker, Jr. [32]
August 18 [33]
August 25 [34]
September 1 "What's Love Got to Do with It" Tina Turner [35]
September 8 [36]
September 15 [37][38]
September 22 "Missing You" John Waite [39][40]
September 29 "Let's Go Crazy" Prince and the Revolution [41]
October 6 [42][43]
October 13 "I Just Called to Say I Love You" Stevie Wonder [44][45]
October 20 [46][47]
October 27 [48][49]
November 3 "Caribbean Queen (No More Love on the Run)" Billy Ocean [50][51]
November 10 [52][53]
November 17 "Wake Me Up Before You Go-Go" Wham! [54][55]
November 24 [56][57]
December 1 [58][59]
December 8 "Out of Touch" Daryl Hall and John Oates [60][61]
December 15 [62][63]
December 22 "Like a Virgin" Madonna [64][65]
December 29 [66]
See also[edit]
1984 in music
List of Cash Box Top 100 number-one singles of 1984
References[edit]
Jump up ^ http://www.billboard.com/charts/1984-01-07/hot-100
Jump up ^ http://www.billboard.com/charts/1984-01-14/hot-100
Jump up ^ http://www.billboard.com/charts/1984-01-21/hot-100
Jump up ^ http://www.billboard.com/charts/1984-01-28/hot-100
Jump up ^ http://www.billboard.com/charts/1984-02-04/hot-100
Jump up ^ http://www.billboard.com/charts/1984-02-11/hot-100
Jump up ^ http://www.billboard.com/charts/1984-02-18/hot-100
Jump up ^ http://www.billboard.com/charts/1984-08-25/hot-100
Jump up ^ http://www.billboard.com/charts/1984-03-03/hot-100
Jump up ^ http://www.billboard.com/charts/1984-03-10/hot-100
Jump up ^ http://www.billboard.com/charts/1984-03-17/hot-100
Jump up ^ http://www.billboard.com/charts/1984-03-24/hot-100
Jump up ^ http://www.billboard.com/charts/1984-03-31/hot-100
Jump up ^ http://www.billboard.com/charts/1984-04-07/hot-100
Jump up ^ http://www.billboard.com/charts/1984-04-14/hot-100
Jump up ^ http://www.billboard.com/charts/1984-04-21/hot-100
Jump up ^ http://www.billboard.com/charts/1984-04-28/hot-100
Jump up ^ http://www.billboard.com/charts/1984-05-05/hot-100
Jump up ^ http://www.billboard.com/charts/1984-05-12/hot-100
Jump up ^ http://www.billboard.com/charts/1984-05-19/hot-100
Jump up ^ http://www.billboard.com/charts/1984-05-26/hot-100
Jump up ^ http://www.billboard.com/charts/1984-06-02/hot-100
Jump up ^ http://www.billboard.com/charts/1984-06-09/hot-100
Jump up ^ http://www.billboard.com/charts/1984-06-16/hot-100
Jump up ^ http://www.billboard.com/charts/1984-06-23/hot-100
Jump up ^ http://www.billboard.com/charts/1984-06-30/hot-100
Jump up ^ http://www.billboard.com/charts/1984-07-07/hot-100
Jump up ^ http://www.billboard.com/charts/1984-07-14/hot-100
Jump up ^ http://www.billboard.com/charts/1984-07-21/hot-100
Jump up ^ http://www.billboard.com/charts/1984-07-28/hot-100
Jump up ^ http://www.billboard.com/charts/1984-08-04/hot-100
Jump up ^ http://www.billboard.com/charts/1984-08-11/hot-100
Jump up ^ http://www.billboard.com/charts/1984-08-18/hot-100
Jump up ^ http://www.billboard.com/charts/1984-08-25/hot-100
Jump up ^ http://www.billboard.com/charts/1984-09-01/hot-100
Jump up ^ http://www.billboard.com/charts/1984-09-08/hot-100
Jump up ^ http://www.billboard.com/charts/1984-09-15/hot-100
Jump up ^ DeKnock, Jan (1984-09-14). "How Long Can Tina Turner Stay No. 1?". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-09-22/hot-100
Jump up ^ DeKnock, Jan (1984-09-21). "John Waite, a New Face on Top of Charts". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-09-29/hot-100
Jump up ^ http://www.billboard.com/charts/1984-10-06/hot-100
Jump up ^ DeKnock, Jan (1984-10-05). "Prince Still Holds No. 1". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-10-13/hot-100
Jump up ^ DeKnock, Jan (1984-10-12). "Stevie Wonder's 'I Just Called' Takes Over 3 Top Spots on the Charts". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-10-20/hot-100
Jump up ^ DeKnock, Jan (1984-10-19). "Stevie's Hit 'I Just Called' Now a Worldwide Wonder". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-10-27/hot-100
Jump up ^ DeKnock, Jan (1984-10-26). "Wonder's 'I Just Called' Continues Grand Slam on Charts". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-11-03/hot-100
Jump up ^ DeKnock, Jan (1984-11-02). "Stevie Wonder Slips to No. 2, but Stays Hot with Worldwide Audience". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-11-10/hot-100
Jump up ^ DeKnock, Jan (1984-11-09). "Here's a Surprise; Top 3 Hits all Hold on to Their Spots Another Week". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-11-17/hot-100
Jump up ^ DeKnock, Jan (1984-11-16). "It's British Band Wham in the No. 1 Spot". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-11-24/hot-100
Jump up ^ DeKnock, Jan (1984-11-24). "Chart Watching". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-12-01/hot-100
Jump up ^ DeKnock, Jan (1984-11-30). "Wham Holds on to Top Rung". Chicago Tribune. Tribune Company. Retrieved 2009-02-01.
Jump up ^ http://www.billboard.com/charts/1984-12-08/hot-100
Jump up ^ DeKnock, Jan (1984-12-07). "Hall & Oates' Smash Hit 'Out of Touch' is Their Fifth No. 1 Pop Single in Four Years". Chicago Tribune. Tribune Company. Retrieved 2009-02-01.
Jump up ^ http://www.billboard.com/charts/1984-12-15/hot-100
Jump up ^ DeKnock, Jan (1984-12-14). "Chart Watching". Chicago Tribune. Tribune Company. Retrieved 2009-04-19.
Jump up ^ http://www.billboard.com/charts/1984-12-22/hot-100
Jump up ^ DeKnock, Jan (1984-12-21). "Madonna Speeds Past Duran Duran to Reach the Top". Chicago Tribune. Tribune Company. Retrieved 2009-02-01.
Jump up ^ http://www.billboard.com/charts/1984-12-29/hot-100
Additional sources[edit]
Fred Bronson's Billboard Book of Number 1 Hits, 5th Edition (ISBN 0-8230-7677-6)
Joel Whitburn's Top Pop Singles 1955-2008, 12 Edition (ISBN 0-89820-180-2)
Joel Whitburn Presents the Billboard Hot 100 Charts: The Eighties (ISBN 0-89820-079-2)
Additional information obtained can be verified within Billboard's online archive services and print editions of the magazine.
hide
v
t
e
Lists of Billboard number-one singles
1940–1959
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960–1979
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980–1999
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000–present
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
By decade
1940s
1950–1958
1958–1969
1970s
1980s
1990s
2000s
2010s
See also
Hot 100 Year-end
List of Billboard Hot 100 chart achievements and milestones
Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_Billboard_Hot_100_number-one_singles_of_1984&oldid=789355397"
Categories:
1984 record charts
Lists of Billboard Hot 100 number-one songs
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Čeština
Deutsch
Español
Français
Italiano
Nederlands
日本語
Polski
Русский
Svenska
Türkçe
Tiếng Việt
中文
4 more
Edit links
This page was last edited on 6 July 2017, at 21:46.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

value: i

values: firstHeading firstHeading en

values: siteSub noprint

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

value: b

values: Billboard Year-End Hot 100 singles of 1984

values: Against All Odds (Take a Look at Me Now)

values:
/wiki/Ray_Parker,_Jr.
mw-redirect
Ray Parker, Jr.

values:
/wiki/Caribbean_Queen
mw-redirect
Caribbean Queen

values: List of Cash Box Top 100 number-one singles of 1984

values:
/wiki/Tribune_Company
mw-redirect
Tribune Company

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values:
nofollow
external text
http://www.billboard.biz

values: Template:Number-one singles in the United States

values: Template talk:Number-one singles in the United States

values: List of Billboard number-one singles of 1940

values: List of Billboard number-one singles of 1941

values: List of Billboard number-one singles of 1942

values: List of Billboard number-one singles of 1943

values: List of Billboard number-one singles of 1944

values: List of Billboard number-one singles of 1945

values: List of Billboard number-one singles of 1946

values: List of Billboard number-one singles of 1947

values: List of Billboard number-one singles of 1948

values: List of Billboard number-one singles of 1949

values: List of Billboard number-one singles of 1950

values: List of Billboard number-one singles of 1951

values: List of Billboard number-one singles of 1952

values: List of Billboard number-one singles of 1953

values: List of Billboard number-one singles of 1954

values: List of Billboard number-one singles of 1955

values: List of Billboard number-one singles of 1956

values: List of Billboard number-one singles of 1957

values: List of Billboard number-one singles of 1958

values: List of Billboard Hot 100 number-one singles of 1959

values: List of Billboard Hot 100 number-one singles of 1960

values: List of Billboard Hot 100 number-one singles of 1961

values: List of Billboard Hot 100 number-one singles of 1962

values: List of Billboard Hot 100 number-one singles of 1963

values: List of Billboard Hot 100 number-one singles of 1964

values: List of Billboard Hot 100 number-one singles of 1965

values: List of Billboard Hot 100 number-one singles of 1966

values: List of Billboard Hot 100 number-one singles of 1967

values: List of Billboard Hot 100 number-one singles of 1968

values: List of Billboard Hot 100 number-one singles of 1969

values: List of Billboard Hot 100 number-one singles of 1970

values: List of Billboard Hot 100 number-one singles of 1971

values: List of Billboard Hot 100 number-one singles of 1972

values: List of Billboard Hot 100 number-one singles of 1973

values: List of Billboard Hot 100 number-one singles of 1974

values: List of Billboard Hot 100 number-one singles of 1975

values: List of Billboard Hot 100 number-one singles of 1976

values: List of Billboard Hot 100 number-one singles of 1977

values: List of Billboard Hot 100 number-one singles of 1978

values: List of Billboard Hot 100 number-one singles of 1979

values: List of Billboard Hot 100 number-one singles of 1980

values: List of Billboard Hot 100 number-one singles of 1981

values: List of Billboard Hot 100 number-one singles of 1982

values: List of Billboard Hot 100 number-one singles of 1983

values: List of Billboard Hot 100 number-one singles of 1985

values: List of Billboard Hot 100 number-one singles of 1986

values: List of Billboard Hot 100 number-one singles of 1987

values: List of Billboard Hot 100 number-one singles of 1988

values: List of Billboard Hot 100 number-one singles of 1989

values: List of Billboard Hot 100 number-one singles of 1990

values: List of Billboard Hot 100 number-one singles of 1991

values: List of Billboard Hot 100 number-one singles of 1992

values: List of Billboard Hot 100 number-one singles of 1993

values: List of Billboard Hot 100 number-one singles of 1994

values: List of Billboard Hot 100 number-one singles of 1995

values: List of Billboard Hot 100 number-one singles of 1996

values: List of Billboard Hot 100 number-one singles of 1997

values: List of Billboard Hot 100 number-one singles of 1998

values: List of Billboard Hot 100 number-one singles of 1999

values: List of Billboard Hot 100 number-one singles of 2000

values: List of Billboard Hot 100 number-one singles of 2001

values: List of Billboard Hot 100 number-one singles of 2002

values: List of Billboard Hot 100 number-one singles of 2003

values: List of Billboard Hot 100 number-one singles of 2004

values: List of Billboard Hot 100 number-one singles of 2005

values: List of Billboard Hot 100 number-one singles of 2006

values: List of Billboard Hot 100 number-one singles of 2007

values: List of Billboard Hot 100 number-one singles of 2008

values: List of Billboard Hot 100 number-one singles of 2009

values: List of Billboard Hot 100 number-one singles of 2010

values: List of Billboard Hot 100 number-one singles of 2011

values: List of Billboard Hot 100 number-one singles of 2012

values: List of Billboard Hot 100 number-one singles of 2013

values: List of Billboard Hot 100 number-one singles of 2014

values: List of Billboard Hot 100 number-one singles of 2015

values: List of Billboard Hot 100 number-one singles of 2016

values: List of Billboard Hot 100 number-one singles of 2017

values: List of Billboard Hot 100 number-one singles of 2018

values: List of Billboard number-one singles of the 1940s

values: List of Billboard number-one singles from 1950 to 1958

values: List of Billboard Hot 100 number-one singles from 1958 to 1969

values: List of Billboard Hot 100 number-one singles of the 1970s

values: List of Billboard Hot 100 number-one singles of the 1980s

values: List of Billboard Hot 100 number-one singles of the 1990s

values: List of Billboard Hot 100 number-one singles of the 2000s

values: List of Billboard Hot 100 number-one singles of the 2010s

values: nowraplinks collapsible autocollapse navbox-inner mw-collapsible mw-made-collapsible

values: Category:Lists of Billboard Hot 100 number-one songs

values:
catlinks mw-normal-catlinks
catlinks mw-normal-catlinks
interface

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values: Singly na prvním místě v roce 1984 (USA) – Czech

values:
interlanguage-link interwiki-cs
display: none;

values: Liste der Nummer-eins-Hits in den USA (1984) – German

values: Anexo:Sencillos número uno de Hot 100 de 1984 (EE. UU.) – Spanish

values: Liste des titres musicaux numéro un aux États-Unis en 1984 – French

values: Singoli al numero uno nella Billboard Hot 100 nel 1984 – Italian

values: Nummer 1-hits in de Billboard Hot 100 in 1984 – Dutch

values:
interlanguage-link interwiki-nl
display: none;

values: 1984年のビルボード・ホット100による1位のシングル一覧 – Japanese

values: Single numer jeden w roku 1984 (USA) – Polish

values:
interlanguage-link interwiki-pl
display: none;

values: Список синглов № 1 в США в 1984 году (Billboard) – Russian

values: Billboardlistans förstaplaceringar 1984 – Swedish

values: 1984'te Billboard Hot 100'da bir numara olan single'lar listesi – Turkish

values: Danh sách đĩa đơn quán quân Hot 100 năm 1984 (Mỹ) – Vietnamese

values: 1984年美国告示牌百强单曲榜冠军单曲列表 – Chinese

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-List_of_Billboard_Hot_100_number-one_singles_of_1984 rootpage-List_of_Billboard_Hot_100_number-one_singles_of_1984 skin-vector action-view