| | |
Assembly is used for?
Please support our Assembly advertiser: Programming Forums - DaniWeb Sister Site
![]() |
•
•
Join Date: Jan 2007
Posts: 49
Reputation:
Solved Threads: 0
•
•
•
•
Anybody who writes a memory resident debugger, which can randomly interrupt the execution of a program at any point, will soon discover that the average app spends about 90% of its time executing operating system code. Therefore it can be as fast as the OS, and no faster.
You seem to be a very GUI/desktop centric person. I assure you, there's a whole world out there you've never seen.
You seem to hold the guts of an OS as some sort of impenetrable black box who's will we a simply subject to. Having spect a significant portion of my career in the guts of OS's and drivers, I can state this is not the case, and the cure for performance issues in OS's is often assembler code. In fact the guts of the OS/2 kernel were virtually all assembler with few exceptions (HPFS was mostly C). Run OS/2 on anything and compare it to Windows or Linux in terms of speed and responsivness. There is no comparason. All that assembler code beats the crap out of the C code systems.
Last edited by Purple Avenger; Feb 1st, 2007 at 8:34 pm.
•
•
Join Date: Jan 2007
Posts: 15
Reputation:
Solved Threads: 0
•
•
•
•
Anybody who writes a memory resident debugger, which can randomly interrupt the execution of a program at any point, will soon discover that the average app spends about 90% of its time executing operating system code. Therefore it can be as fast as the OS, and no faster.
My conclusion: Assembly language can produce by far the fastest and smallest binaries, it is as easy (or difficult) as any other programming language. One can be AT LEAST as productive as can be with any other language because he/she will not be fighting with the HLL's limitations.
Antonis
•
•
Join Date: Nov 2006
Posts: 134
Reputation:
Solved Threads: 3
•
•
•
•
Its a very bold (and 100% wrong) assumption that all computer systems have an OS or one that they're CPU bound upon.
You seem to be a very GUI/desktop centric person. I assure you, there's a whole world out there you've never seen.
You seem to hold the guts of an OS as some sort of impenetrable black box who's will we a simply subject to. Having spect a significant portion of my career in the guts of OS's and drivers, I can state this is not the case, and the cure for performance issues in OS's is often assembler code. In fact the guts of the OS/2 kernel were virtually all assembler with few exceptions (HPFS was mostly C). Run OS/2 on anything and compare it to Windows or Linux in terms of speed and responsivness. There is no comparason. All that assembler code beats the crap out of the C code systems.
Most people aren't involved in writing operating systems - they are involved in writing apps. As it happens, the operating system I was referring to, with apps spending 90% of their time inside it, wasn't a GUI system.
Personally, I hadn't noticed Windows graphics being particularly slow; we are no longer in the age of 4.77MHz PC's, where every last clock cycle counted.
•
•
Join Date: Jan 2007
Posts: 49
Reputation:
Solved Threads: 0
Last edited by Purple Avenger; Feb 2nd, 2007 at 7:50 pm.
•
•
•
•
And YOUR conclusion is: no matter what language you use or what code you write, final binaries will have the same speed ...
•
•
•
•
My conclusion: Assembly language can produce by far the fastest and smallest binaries
•
•
•
•
One can be AT LEAST as productive as can be with any other language because he/she will not be fighting with the HLL's limitations.
Don't PM me with questions -- you might get a nasty PM in response. If you have a question then post it in one of the forums.
•
•
Join Date: Jan 2007
Posts: 49
Reputation:
Solved Threads: 0
•
•
•
•
why no one writes anything but trivial programs in assembly language.
In the 1.X and GA 2.0 version the PM graphics engine was assembler as well. The VGA and 8514 drivers was all assembler and large chunks of the XGA driver were assembler.
Gibson claims everything he does is assembler. don't know if that's true or not, but its what he claims.
I've got a 100,000 LOC test suite for the DOS Int 21 API that's done all in assembler.
•
•
Join Date: Jan 2007
Posts: 15
Reputation:
Solved Threads: 0
•
•
•
•
Not so -- bad compilers or unoptimized code will produce slower binaries. Different compilers will produce very different binaries (*.exe) even with the same source code. That is one of the bench mark test that many companies perform on compilers.
•
•
•
•
Yes it could, but whether it does not not is highly dependent on the skills of the programmer.
•
•
•
•
Assembly language is the LEAST productive of all languages
•
•
•
•
not very useful for anyone other than those who design write compilers or operating systems
I am really wondering why one spends his time in an Assembly forum trying to persuade people that they are not productive! I hope it doesn't sound like and ad, my site (and many others) is a proof of what I am saying.
Antonis
![]() |
Similar Threads
- Questions about assembly and boolean algebra (Assembly)
- Assembly Programming Question (Assembly)
- How can i use inline assembly in VC++ editor (C++)
- Mips Assembly porting from C (Assembly)
- machine/assembly language, syntax error (C++)
- Using x86 Assembly Language with Microsoft Visual C++ (C++)
Other Threads in the Assembly Forum
- Previous Thread: 8 Queens Problem!?
- Next Thread: drag & drop
| Thread Tools | Search this Thread |
Tag cloud for Assembly






