6 ms·
I'm a little confused - why is ASM still an issue these days? Sure I can understand some in-line ASM for hardcore speed-critical code but beyond that...why both
by Havoc 12y ago
I'm a little confused - why is ASM still an issue these days? Sure I can understand some in-line ASM for hardcore speed-critical code but beyond that...why bother? Even interpreted langs seem fast enough these days, so compiled should def be fast enough and resorting to ASM should imo be unnecessary.
NB the above is a personal view & I'm not a programmer by profession...so if I missed something - no offence intended.
- sliverstorm 12y agoIt's probably a pet project for fun & learning about the metal.
- ChuckMcM 12y agoIt is the difference between passion and education. Someone who passionate about technology is really interested in all the bits and crevices, someone who is simply learned about technology classifies knowledge into 'useful' and 'not useful' parts. A common example is 'car people' who go through and re-design the fuel injectors for their car. It isn't "required" but they really like everything about all the pieces. So they persevere to understand it all.
- bsoares 12y agoThis is a very well thought statement. I was just thinking this morning how great is to understand low level logic and coding, but when discussing it with a co-worker, it was clear that there was no practical day to day benefit from knowing about the underpinnings of the higher level languages we use. That said, I am able to better overcome technical challenges when they arise due to my curiosity and passion for the details.
- Havoc 12y agoI hear you. Though in the modern world I feel everyone is forced to triage on the useful/not useful front. There is too much info out there and not enough time.
- pjmlp 12y agoSomeone needs to write bootloaders, OS drivers, compilers, interpreters, image processing algorithms, audio processing filters, ...
- xooxies 12y agoIt's still a need to know if you work in the reverse engineering, security, vulnerability analysis, etc. realms.
- krylon 12y agoWell, there's always people that just think it's fun. Plus, you learn A LOT about the processor you are working with. But the group of programmers who need to work in assembly is not very large, I think. Most of them are probably writing compiler backends or working in embedded systems. But learning assembly teaches you a lot about how the processor works, so it might be time well spent even if you never actually write assembly. (NB I don't really know assembly, I have written like 20 instructions of inline assembly (and 3 inline binary instructions - what a rush that was!), so I am not an expert on the matter, but I can see the appeal. ;-)
- jonhess 12y agoIf you're writing a desktop app, you may need to debug frameworks and libraries you don't have the source for. If you author a framework or library, you may need to debug a client application you don't have source for. In both cases, you'll likely need to debug assembly code.
- minimax 12y agoWhen you are profiling code that's been generated by an optimizing compiler, you often have to manually reverse-translate from the compiler generated assembler back into the C/C++ source to understand the profile results. The reason you have to do it manually is because one line of C or C++ can easily be compiled into a dozen or more instructions which may not even be adjacent to each other. I don't write much assembler but I find myself reading assembler at least once a week.
- alecco 12y agoASM is great for learning how CPUs work. Also it's central for: * building compilers, especially JIT * debugging binaries * the lowest level of kernels * understanding security exploits like overflows, format string, JIT spraying * hardcore performance
- jwr 12y agoThe definition of "fast enough" varies. A while ago, I was doing some exploratory work — basically trying out various approaches to a problem. There was a particular piece of code that was quite expensive to execute and that was executed a lot. The net result was that a single calculation of the required matrix took about two months. It took more than a month of hard, full-time work to fit the problem into fixed-point registers and the SIMD model used by Intel SSE. Over two weeks from that month were spent on debugging, even though I went through multiple versions in C, each one closer to the target assembly. But the resulting speedup was well worth it: about 600x. Now think about it. 600x. We went from "a single try/iteration takes two months" to "we can try six variations overnight". So yes, assembly matters, for many reasons of which I only outlined one. As a side note, people tend to focus on big-O algorithm performance, neglecting the constant. But the constant matters in practice, more than most people think.
- Havoc 12y ago>The definition of "fast enough" varies. You list one specific example where ASM provided a tangible speed benefit in a research oriented processing heavy env.. Indeed. Now take a good look at my original comment: >>Sure I can understand some in-line ASM for hardcore speed-critical code
- floody-berry 12y agoEr, do you think only a select few people need to know assembler then?
- radmuzom 12y agoEven though I don't advocate application programmers using assembly, I strongly disagree with your statement "Even interpreted langs seem fast enough these days". This is true probably for a small subset of programmers who are mostly into web programming (and using the logic that network and not the CPU is the bottleneck which is plain nonsense), but not true for programmers who create useful applications used by many companies around the world. To give some examples not necessarily related to interpreted languages but to show how fast software is getting worse and worse, 1. My Windows 2000 start-up time on a 1GB machine was probably slightly higher (4-5 seconds) than Windows 8 start-up time in a 8GB machine. It looks like improvements in hardware have not made any difference to the user experience. Similar for Linux, but that may be driven by distributions bundling more things at start-up. 2. In Excel 2003, I could right-click on a cell and format - the formatting dialogue would open up instantly. In Excel 2010, I need to wait 2-3 seconds for the dialogue to open up. 3. I regularly use software like TOAD and SAS at work. Given that both are often used to examine data, I need them to work very smoothly after they have retrieved the necessary data from the back-end database. TOAD is ok, but SAS has gotten progressively worse over the years. I don't care whether your developer time is costlier than compiler time, I need the software to work as fast as it can only constrained by the specifications of my machine. 4. Laptop at work is encrypted using Symantec products. The software is so bad that the hard disk light on the laptop just keeps on "glowing", indicating HD activity, continuously without EVER stopping. All applications are slowed down too because of this activity. I could just go on and on about how software is getting worse day by day. Even John Carmack recently tweeted about this - how smartphones with massive processing power and small resolutions can't display graphics decently as compared to very old machines. Anyway, thanks for letting me vent out my frustration which has been building up for quite a few days now.
- userbinator 12y agoI don't care whether your developer time is costlier than compiler time, I need the software to work as fast as it can only constrained by the specifications of my machine. I can't agree more. Many programmers are traditionally taught that optimisation is some sort of "last moment" effort for when thing are seriously bloated and slow and that programmer time is more expensive than machine time, and it seems all this does is breed a lazy, selfish attitude; yes, it's very likely not worth expending an hour or even 10 minutes to optimise a throwaway script that's used by yourself and isn't a bottleneck in your process, but when your software is used by hundreds, thousands, or even millions or more users worldwide, who are often paying users, it doesn't seem nice at all to be making them all wait or be forced to buy newer hardware just so you can "save" a bit of work that you should be doing anyway. It's like http://xkcd.com/1205/ http://xkcd.com/1205/ , multiplied by the size of the userbase.
- userbinator 12y agoAs someone who reverse-engineers and has seen a lot of compiler-generated code as a result, I'm even more convinced than before that the whole "compilers are better at generating code" mantra is a myth. The only thing they're good at in practice is generating lots of code quickly; there are instances when the output of a compiler manages to impress me (Intel's is particularly good at that), but they're still quite isolated instances and the rest of the code continues to have this "compiler-generated" look to it, i.e. much could be improved. It is certainly not hard to beat a compiler on speed or size (often both), and I believe that the only ones who can't are the ones who learnt Asm the stupid way that compilers generate code and not how the machine really works. E.g. it's commonly taught that x86 has 6 general-purpose registers (reserving eBP/eSP), but in reality eBP-based stack frames and the use of the stack is nothing more than a compiler-generated artificial construct. Even eSP can be used for something else if you really need one more register[1]! Compilers follow the rules of their source language and impose strict, often unnecessary conventions on their output. Asm follows the rules of the machine, which are far richer and more expressive than the abstracted simplicity of any HLL. That being said, they have improved significantly over the years - the days when compilers would push/pop every register on entry/exit to a function regardless of whether it was used (or its caller needed the value preserved), or when the start of every function could be identified by a distinctive 55 89 E5 (push bp; mov bp, sp) in the binary are fortunately mostly history. [1] http://www.virtualdub.org/blog/pivot/entry.php?id=85 http://www.virtualdub.org/blog/pivot/entry.php?id=85
- Havoc 12y agoYou miss my point 100%. I know ASM code is technically superior. However, the advances in tech have outpaced the advantages of ASM. Yes your code is 10x more efficient than mine, but I can throw 1000x as much processing power at this via cloud & a scripting languages. Yes you've seen more "compiler-generated code" than I have but realistically...who is going to win this p!ssing contest? You writing ASM code or me scaling a scripting language across clouds? I bet I can deploy cloud processing power faster than you can MOV AX,CS MOV DS,AX Also - I'm not in the cloud game - the above is a simple example/play the devils advocate.
- 12y ago
- scott_s 12y agoAssembly is part of how a computer computes, and there are people who want to understand every step of the process. Such people are not satisfied until they can pull back the covers, and say to themselves "Aha! I get it, this little thing here feeds into this thing here... which goes there... and out comes my answer. Cool." And it's a good thing such people exist, because they build all of the foundational technology that you take for granted.
- lovelearning 12y agoIn a past life, I worked in an industry where just about all components of our large software system were written in C++. Lots of multithreading, memory allocations, deallocations, etc. If there is one thing C++ developers know better than the language itself, it's debuggers and memory dumps. We used tools like windbg and gdb almost as much as the IDE. Often, crash dumps from our release binaries didn't have enough inbuilt information to find the cause of the crash. We would then have to do things like walking the stack manually. For doing that effectively, it was necessary to understand x86 internals to figure out what the disassembled code is doing. This is probably the likeliest way most native application developers run into assembly language. Always helps to know it well.
- DCoder 12y agoThere are other uses for ASM aside from getting more speed. Learning ASM will show you how things work at a low level, which is helpful when you try to understand C pointers and other details. Reading assembly also lets you (try to) understand the programs you don't have the source for - device drivers¹, malware¹, copy-protection, regular third-party applications ... I spent several years disassembling a game (C&C Red Alert 2), understanding the code, fixing the shitty parts and glitches left in it, and extending it. It was fascinating. ¹These examples are certainly far from trivial, I know, but that is half the fun.