7 ms·
Say hello to x64 Assembly, part 1
- lovelearning 12y agoExcellent! Just 2 days ago, somebody here was complaining about shortage of asm programmers, and I suggested them that I'd personally be interested in a hello world x86_64 tutorial to rekindle my interest in asm...and today I see this posted! Exactly what I wanted, thank you.
- melling 12y agoI think ARM assembler might be more useful because of all the mobile devices and Raspberry Pi's.
- pjc50 12y agoIndeed - I've found being able to read ARM assembler extremely useful, especially when dealing with buggy closed source libraries or doing WinCE development. Haven't had cause to write very much though. Writing assembler is really only useful when you're doing vectorised or other high-performance arithmetic on the CPU.
- innocenat 12y agoI still don't understand why people who want to learn amd64 assembly won't read x86 tutorial. I write both x86 and amd64 assembly from time to time, and I don't think there are anything that make x86 tutorial/manual not applicable to amd64. Sure, there are differences: register name, C ABI convention, system calls, memory modes, etc. But those information can be find easily in references. And you need reference for x86 anyway. Otherwise all mechanisms are the same.
- lovelearning 12y agoWith so many other things to learn and ideas to implement, something like assembly programming sits way back on the backburner. It's only recreational for me, not something critical for my work. An easy tutorial like this injects just the right amount of motivation to atleast dip my feet back in. Having to wade through Intel's 1000 page system manuals to check if my past knowledge is useful or not, would require a lot more motivation than I can muster.
- amenod 12y agoFor experienced programmer this is most certainly true. If you are just starting however it is much easier if tutorial uses the same platform you are targeting.
- ANTSANTS 12y agoIt's a bit of a catch-22: you can't know that there's not much different between x86 and x86-64 until you understand both. I guess asm newbies have some kind of mistaken idea that x86 is irrelevant and not worth their time learning (even if it were completely dead in the wild, which it absolutely isn't, you still need to know it truly understand the architecture); I've tried to post older x86 and ARM assembly language guides, much better written and more in-depth than this article (no offense intended to the author), and the only comments I get are along the lines of "this is old, it doesn't even cover x86-64/ARM64."
- CraigJPerry 12y agoAnother great resource, albeit for x86 rather than 64 http://savannah.nongnu.org/projects/pgubook/ http://savannah.nongnu.org/projects/pgubook/
- pekk 12y agoIt isn't nearly as hard to find x86 guides as x86-64 guides.
- 0xAX 12y agoThat's why i started to write it :)
- CraigJPerry 12y agoIn what material way, in the context of a beginners guide, are they different? Calling convention, word size and the r- prefixes. If you compete the PGU book (you could just write 32 bit code if you want), these are trivialities.
- jpgvm 12y agoBeing able to read x64 assembler even if you can't write it is great for debugging strange issues.
- NaNNaNNaNNaN 12y agoJavascript is the assembly language of today. For debugging purposes you're better off with Javascript.
- ThatOtherPerson 12y agoNot everybody targets all their code for the web.
- rev_bird 12y agoYou mean there's code... not on the web?!
- mikeash 12y agoOh yeah, that'll totally help when debugging my iOS or Android code.
- MrBuddyCasino 12y agoIf you use humor or irony here without adding any substance to the discussion, one of two things will happen: - it will not be understood, you might get downvoted - it will be understood and you'll definitely get downvoted
- nl 12y agoAlso great is being able to read JVM bytecode. Even minor changes can be pretty interesting. Back in the day I wrote [1] about simple Java string concatenation. I still get people quoting it now, even though I'm sure it is completely outdated by newer compilers. It gets even more interesting when you see what x64 (or whatever!) assembly is generated by the JVM. [1] http://nicklothian.com/blog/2005/06/09/on-java-string-concatenation/ http://nicklothian.com/blog/2005/06/09/on-java-string-concat...
- okasaki 12y agoThe code doesn't render with links2. Does it rely on javascript?
- krakensden 12y agoYup- they're gists. I'm pretty sympathetic, setting up pygments, etc., is sort of a pain.
- robert_tweed 12y agoDoes anyone know what's a good macro-assembler these days? The article recommends NASM, but I don't know if it's comparable to MASM for larger, more complex projects. I rather fancy getting back into writing asm, just to sharpen that skill. I haven't really written any since MASM 6.x on DOS, 20-ish years ago. I actually found it quite enjoyable and it's surprising how complex an application you can write from scratch in assembly without it becoming unmanageable, so long as you get into the right mindset and make effective use of macros. Of course, any significant piece of assembly code is likely to contain considerably more bugs than just about anything else of the same complexity. You'll also experience a lot more segfaults during development than perhaps most are comfortable with, but there's something rewarding about controlling precisely what the machine is doing at that level. This is especially true if you manage to find a novel solution that just wouldn't exist when the hardware capabilities are abstracted away by a high level language. In the same way that everyone should learn a Lisp to think in terms of ASTs and code-as-data, everyone should write at least one whole application in assembly just to appreciate how the hardware really works. Also to see how often there are many ways to solve the same problem (especially with an x86 instruction set), sometimes with wildly different performance characteristics.
- RDeckard 12y agoFASM: http://www.flatassembler.net/ http://www.flatassembler.net/
- robert_tweed 12y agoWell, digging around the docs and FAQs on both sites I couldn't see much useful introductory information about what the unique features of either project are, but I did some further Googling and read a few discussions. For anyone else interested, my conclusions are: NASM and FASM are really the only up-to-date and cross-platform capable assemblers. MASM is up to date, but Windows only. TASM is not up to date. Others appear to have been abandoned. The differences: NASM: Is written in C and generates object files. Requires a linker to produce executables. Slow, inefficient compilation. Has some syntax quirks. May be more flexible in some cases due to the multiple object formats available. FASM: Written in FASM. Very fast compilation. Cleaner syntax, better debugging tools. Produces executables directly without a linker. Possibly limited due to smaller number of output formats, but likely good enough for most projects that would be written in pure asm anyway. FASM looks like the best option to learn first and then move to NASM for any specific requirement that FASM cannot meet. The syntax is mostly compatible between the two, so porting code shouldn't be too much trouble in the worst case.
- 31reasons 12y agoIts funny after so many years Code is still called Text in assembly.
- robert_tweed 12y agoThat's not the way I remember it in MASM/DOS. I think it's a Unix-specific thing.
- DigitalJack 12y agodesertmonad has a gist with 32bit and 64bit hello world's for osx. https://gist.github.com/desertmonad/36da2e83569bc8b120e0 https://gist.github.com/desertmonad/36da2e83569bc8b120e0
- theoutlander 12y agoThanks for the writeup. I'm going to try it one of these days when I get a break from work/startup. I ordered a few books recently and have been tinkering with writing an OS....got as far as writing a bootloader and then switched gears into learning ASM. I bought Peter Norton's Assembly Language Book for the IBM PC. This book is pretty awesome and so relevant even 25 years later!! It covers the basics really well and stops at 386 (the latest proc then) so I don't feel inundated with hundreds of CPU architectures. Yes, I'll eventually get to those. The other two books (in case anyone else is interested): X86 Assembly Language and C Fundamentals by Joseph Cavanagh. Operating Systems Design and Implementation (3rd Edition). Also, while tinkering with ASM I decided to install MSDOS since the ASM book uses Debug.exe and I couldn't seem to find it for newer OS's. While looking to download MSDOS, I discovered the source code for MSDOS 1.1 & 2.0 @ http://www.computerhistory.org/atchm/microsoft-research-license-agreement-msdos-v1-1-v2-0/ http://www.computerhistory.org/atchm/microsoft-research-lice....
- infoseckid 12y agoYou guys might enjoy this http://www.pentesteracademy.com/course?id=7 http://www.pentesteracademy.com/course?id=7
- e12e 12y agoI came across Intel's intro to x64 assembly when I was looking for some information on working with wide characters on 64bit (I seem to recall there were some new instructions introduced for that, I'm guessing one would probably be better off using libicu to parse eg: utf-8 into some form of 16-bit characters first, though?). Anyway, nothing on wide characters, but essentially a work-a-like hello-world for Microsoft Windows and MASM: https://software.intel.com/en-us/articles/introduction-to-x64-assembly https://software.intel.com/en-us/articles/introduction-to-x6...