www.archive-org-2013.com » ORG » X » X86-64

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 216 . Archive date: 2013-11.

  • Title: AMD64 Homepage
    Descriptive info: .. about.. contributors.. downloads.. documentation.. mailing lists.. CVS access.. Welcome to the Source.. This site is dedicated to porting open source software to the AMD64 architecture, including: GNU/Linux, FreeBSD, NetBSD and OpenBSD..

    Original link path: /
    Open archive

  • Title: AMD64 Subpage
    Descriptive info: AMD and industry partners have launched this website to enable developers to begin incorporating AMD64 technology support in their operating systems, applications, drivers, and development tools.. AMD64.. org is a community website aimed at open source developers.. This site is administered and maintained by the Server Operating Systems team which is an.. AMD.. department that deals in particular with Open Source development for the AMD64 architecture.. Questions? Send mail to the appropriate.. mailing list..

    Original link path: /about.html
    Open archive

  • Title: AMD64 Contributors
    Descriptive info: This page lists some of the people who have contributed to the AMD64 technology ports of open source software.. If you know of people missing from this list (and there are probably a bunch!) send mail to.. info@x86-64.. org.. If you'd like to see your name in lights, join the.. , and see what's happenning.. You'll find something to do soon enough!.. David O'Brien..  ...   binutils.. Andreas Jaeger.. AMD64 architecture support, GNU/Linux port, GCC.. Bo Thorsen.. AMD64 architecture support, GNU/Linux port, binutils, ABI tests, GCC port.. Peter Wemm.. FreeBSD.. Frank van der Linden.. NetBSD, GCC, binutils.. Jiri Smid.. GDB.. Egbert Eich.. XFree86.. Benjamin Chelf.. SimNow Simulator port.. Alexander Samuel.. Andi Kleen.. GNU/Linux kernel development.. Andrea Arcangeli.. Vojtech Pavlik.. Alex Dreyzen.. ABI design.. ABI design, Glibc port, Site administration.. Pavel Machek..

    Original link path: /contributors.html
    Open archive

  • Title: AMD64 Subpage
    Descriptive info: Here's what all you kernel hackers have dreamed of.. : an x86 system simulator running under GNU/Linux! The simulated system contains an AMD64 technology-enabled chip, RAM, disks, and VGA.. You can single-step the CPU, peek at registers and memory, and lots of other fun stuff.. You can run 64-bit and 32-bit GNU/Linux, can play with 64-bit mode, and you can debug those pesky kernel bugs without having to hard-boot your  ...   made available some assembly code definitions that might be useful in developing kernel and/or driver code.. These definitions provide assembly code definitions for structures that map directly onto the hardware, such as the processor TSS structures.. These assembly files are written for the MASM assembler.. To download the files, you have to agree to the.. license agreement.. Toolchain.. Please use the latest official releases of.. GCC.. ,.. glibc.. , and.. binutils..

    Original link path: /downloads.html
    Open archive

  • Title: AMD64 Subpage
    Descriptive info: Documentation.. Gentle Introduction to x86-64 Assembly.. ABI.. AMD64 Application Binary Interface (v 0.. 99).. (aka.. abi.. pdf.. )..

    Original link path: /documentation.html
    Open archive

  • Title: AMD64 Subpage
    Descriptive info: The old mailing list for talking about AMD64 architecture is now defunct.. A new google group will be created for this purpose.. This page will be updated to point to the google group that will be created.. The archives for the old mailing list (particularly 'discuss@x86-64.. org' and 'amd64-microcode@x86-64.. org') are being made available here.. You can search the mailing list archives:.. You can view the archive by using the links below.. Name.. Archive.. discuss@x86-64.. org.. archive.. amd64-microcode@x86-64..

    Original link path: /mailinglists.html
    Open archive

  • Title: AMD64 Subpage
    Descriptive info: cvs access.. The online CVS archives contain the AMD64 ABI specification, gdb, the Linux kernel and some other packages that we needed or worked on.. The archives contain also the ports of GCC, binutils and glibc.. Since all our patches have been moved into the official sources, those repositories here are not maintained any more and have been renamed.. All work is now done in the official CVS repositories which are documented at the home pages of the projects:.. http://gcc.. gnu.. http://sources.. redhat.. com/binutils.. com/glibc.. Online SVN Archive.. You can browse the SVN repository.. online..

    Original link path: /cvsaccess.html
    Open archive

  • Title: AMD64 Subpage
    Original link path: /amd_license.html
    (No additional info available in detailed archive for this subpage)

  • Title: AMD64 Subpage
    Descriptive info: Introduction.. This document is meant to summarise differences between x86-64 and i386 assembly assuming that you already know well the i386 gas syntax.. I will try to keep this document up to date until official documentation is available.. Register set extensions.. X86-64 defines eight new integer registers named r8-r15.. These registers are encoded using special REX prefix and so using them in non-64-bit instruction implies instruction length growth by 1 byte.. They are named as follows:.. rXb for 8 bit register (containing the lowest byte of the 64-bit value) rXw for 16 bits rXd for 32 bits rX for 64 bits.. Where X stands for integer in the range of 8 to 16.. Original integer registers keeps their irregular names and the 64-bit versions of the 32-bit registers eax, edx, exc, ebx, esi, esi, edi, esp and ebp are now called rax, rdx, rcx, rbx, rsi, rdi, rsp and respectivetly rbp.. The new registers can be used in the same places as the old ones, except for implicit register usage.. Some instructions implicitly use specific fixed registers, e.. g.. as shift counters, source and destination for string operations, etc.. Extended 8-bit instructions.. Instructions with REX prefix change behaviour of 8-bit register parts so that all registers can be accessed as 8-bit registers.. The upper halves (ah, dh, ch, bh) are replaced by lower halves of next 4 registers (sil, dil, spl, bpl).. Then the rules described above are applied.. Unfortunatly some instructions require a REX prefix, so you can't use upper halves together with addresses requiring REX prefix:.. addb %ah, (%r10) # Invalid instruction.. 64bit instructions.. By default most operations remain 32-bit and the 64-bit counterparts are invoked by the fourth bit in the REX prefix.. This means that each 32-bit instruction has it's natural 64-bit extension and that extended registers are for free in 64-bit instructions.. To write 64bit instructions, use 'q' as a suffix (q for 'quad-word'):.. movl $1, %eax # 32-bit instruction movq $1, %rax # 64-bit instruction.. Exceptions from this rule are instructions manipulating the stack (push, pop, call, ret, enter and leave) which are implicitly 64-bit and their 32-bit counterparts are not available anymore, yet their 16-bit counterparts are.. So:.. pushl %eax # Illegal instruction pushq %rax # 1 byte instruction encoded as pushl %eax in 32 bits pushq %r10 # 2 byte instruction encoded as pushl preceeded by REX.. Implicit zero extend.. Results of 32-bit operations are implicitly zero extended to 64-bit values.. This differs from  ...   $symb, %eax # 5 byte instruction movq $symb, %rax # 7 byte instruction.. So in case you know that the symbol is in the first 32 bits, you should use 32bit instructions whenever possible.. To load a symbol as 64-bit value, you need to use movabs instruction, that is a synonym for mov only changes the default behaviour:.. movandq %symb, %rax # 11 byte instruction.. Displacements.. Similarly as immediates, the displacements are also sign extended and pretty much the same rules apply to them.. X86-64 defines a special form of move instruction having 64-bit displacement and similarly, as for immediates, it is implicitly used when the value is known to not fit at compilation time and you need to use movabs to force a 64-bit relocation:.. movl 0x1, %eax # load with 32bit sign extended relocation movl 0xffffffff, %eax # load with 64bit relocation movl symb, %eax # load with 32bit sign extended relocation movabsl symb, %eax # load with 64bit sign extended relocation.. Loads and stores with 64-bit displacement are available only for the eax instruction.. RIP relative addressing.. X86-64 defines a new instruction pointer relative addressing mode to simplify writing of position independent code.. The original displacement-only addressing of are overwritten by this one and displacement only is now encoded by one of the redundant SIB form.. This means that RIP relative addressing is actually cheaper than displacement only.. To encode this addressing, just write rip as yet another register:.. movl $0x1, 0x10(%rip).. will store the value 0x1 10 bytes after the end of the instruction.. Symbolic relocation will be implicitly RIP relative, so.. movl $0x1, symb(%rip).. Will write 0x1 to the address of symbol "symb".. FIXME: This looks particularly confusing in the Intel syntax [symb+rip] suggest different location than [symb].. Suggestions for better syntax with symbols?.. You are recommended to use RIP relative addressing whenever possible to reduce code size.. The RIP relative branch instructions are still encoded equally to 32bit mode.. This means that they are implicitly RIP relative and "*" is used to switch to absolute form.. R13 addressing limitations.. The R13 is upper-half equivalent of RBP, that is used in MODRM encoding to escape out into SIB.. The R13 also does the encoding (to prevent REX prefix from changing instruction length), so pretty much same limitations to RBP addressing apply to the R13.. This means that.. (%rbp,index,scale).. is not encodable and:.. 0(%rbp,index,scale).. must be used.. This text was written by Jan Hubicka.. Please send comments to..

    Original link path: /documentation/assembly.html
    Open archive

  • Title: The discuss Archives
    Descriptive info: The discuss Archives.. You can get.. more information about this list.. View by:.. Downloadable version.. September 2012:.. [ Thread ].. [ Subject ].. [ Author ].. [ Date ].. [ Gzip'd Text 716 bytes ].. June 2012:.. [ Gzip'd Text 3 KB ].. May 2012:.. [ Gzip'd Text 2 KB ].. April 2012:.. [ Gzip'd Text 1 KB ].. March 2012:.. [ Gzip'd Text 18 KB ].. February 2012:.. [ Gzip'd Text 7 KB ].. January 2012:.. December 2011:.. [ Gzip'd Text 17 KB ].. July 2011:.. [ Gzip'd Text 438 bytes ].. May 2011:.. [ Gzip'd Text 688 bytes ].. April 2011:.. February 2011:.. December 2010:.. November 2010:.. October 2010:.. [ Gzip'd Text 5 KB ].. September 2010:.. July 2010:.. April 2010:.. March 2010:.. [ Gzip'd Text 6 KB ].. February 2010:.. January 2010:.. December 2009:.. [ Gzip'd Text 10 KB ].. November 2009:.. [ Gzip'd Text 8 KB ].. September 2009:.. [ Gzip'd Text 431 bytes ].. August 2009:.. July 2009:.. June 2009:.. [ Gzip'd Text 14 KB ].. May 2009:.. [ Gzip'd Text 12 KB ].. April 2009:.. March 2009:.. February 2009:.. [ Gzip'd Text 16 KB ].. January 2009:.. December 2008:.. November 2008:.. October 2008:.. [ Gzip'd Text 4 KB ].. September 2008:.. August 2008:.. July 2008:.. [ Gzip'd Text 13 KB ].. June 2008:.. [ Gzip'd Text 43 KB ].. May 2008:.. [ Gzip'd Text 11 KB ].. April 2008:.. March 2008:.. February 2008:.. [ Gzip'd Text 24 KB ].. January 2008:.. December 2007:.. [ Gzip'd Text 15 KB ].. November 2007:.. October 2007:.. September 2007:.. [ Gzip'd Text 25 KB ].. August 2007:.. [ Gzip'd Text 77 KB ].. July 2007:.. June 2007:.. May 2007:.. [ Gzip'd Text 47 KB ].. April 2007:.. [ Gzip'd Text 32 KB ].. March 2007:.. [ Gzip'd Text 30 KB  ...   2005:.. [ Gzip'd Text 60 KB ].. May 2005:.. [ Gzip'd Text 59 KB ].. April 2005:.. [ Gzip'd Text 62 KB ].. March 2005:.. [ Gzip'd Text 68 KB ].. February 2005:.. January 2005:.. [ Gzip'd Text 106 KB ].. December 2004:.. November 2004:.. [ Gzip'd Text 86 KB ].. October 2004:.. [ Gzip'd Text 75 KB ].. September 2004:.. [ Gzip'd Text 46 KB ].. August 2004:.. [ Gzip'd Text 89 KB ].. July 2004:.. [ Gzip'd Text 82 KB ].. June 2004:.. [ Gzip'd Text 72 KB ].. May 2004:.. April 2004:.. [ Gzip'd Text 26 KB ].. March 2004:.. [ Gzip'd Text 55 KB ].. February 2004:.. [ Gzip'd Text 63 KB ].. January 2004:.. [ Gzip'd Text 112 KB ].. December 2003:.. [ Gzip'd Text 27 KB ].. November 2003:.. [ Gzip'd Text 40 KB ].. October 2003:.. September 2003:.. August 2003:.. July 2003:.. June 2003:.. May 2003:.. [ Gzip'd Text 210 KB ].. April 2003:.. March 2003:.. February 2003:.. [ Gzip'd Text 31 KB ].. January 2003:.. [ Gzip'd Text 29 KB ].. December 2002:.. November 2002:.. October 2002:.. [ Gzip'd Text 22 KB ].. September 2002:.. [ Gzip'd Text 54 KB ].. August 2002:.. [ Gzip'd Text 28 KB ].. July 2002:.. June 2002:.. May 2002:.. April 2002:.. [ Gzip'd Text 19 KB ].. March 2002:.. February 2002:.. January 2002:.. December 2001:.. November 2001:.. October 2001:.. September 2001:.. August 2001:.. July 2001:.. June 2001:.. May 2001:.. April 2001:.. March 2001:.. [ Gzip'd Text 99 KB ].. February 2001:.. January 2001:.. [ Gzip'd Text 88 KB ].. December 2000:.. [ Gzip'd Text 70 KB ].. November 2000:.. [ Gzip'd Text 78 KB ].. October 2000:.. [ Gzip'd Text 136 KB ].. September 2000:.. [ Gzip'd Text 320 KB ].. August 2000:.. [ Gzip'd Text 67 KB ]..

    Original link path: /pipermail/discuss/
    Open archive

  • Title: The amd64-microcode Archives
    Descriptive info: The amd64-microcode Archives.. [ Gzip'd Text 9 KB ].. August 2012:.. July 2012:.. November 2011:.. October 2011:.. August 2011:.. March 2011:.. [ Gzip'd Text 420 bytes ].. January 2011:.. [ Gzip'd Text 592 bytes ].. [ Gzip'd Text 576 bytes ].. October 2009:.. [ Gzip'd Text 733 bytes ].. [ Gzip'd Text 491 bytes ]..

    Original link path: /pipermail/amd64-microcode/
    Open archive


  • Archived pages: 216