Miscellaneous > Programming & Networking

Do you know any GOOD books for Assembly for Linux?

<< < (3/3)

ahri:
First of all, there is plenty of information at intel.com on the subject. They have all kinds of developer stuff. The homepage for the P4 is http://developer.intel.com/design/pentium4/index.htm?iid=search+Pentium4c&
Check it out.

The books you can order are here http://developer.intel.com/design/Pentium4/manuals/
You can download the books in pdf format if you don't want to order them. When you call to order, you need the order number of the book you want. You might also want to ask if the books are still free, you never know. To order the books, there is an 800 number you have to call, unfortunatly, i lost it  :(  

I did, however, find a number on the inside of one of the books. Its 1-800-879-4683. I have know idea what number that is for, but you might as well try it. If its the wrong one let me know.

beltorak0:
Assembly was my first real language (basic doesn't count); I used it for years.  Assembly is great for gaining speed, reducing size, and writing tight code.  I was using high level flow control concepts long before I began dabbling in C (switch case, if then elseif, while, etc); constructed a few linked lists and doubly linked lists, manipulated a few two-dimensional arrays of pointers to a mix of functions and data...  The best thing you can learn from assembly is not the interrupts (which are os and chip dependant) but program flow and data manipulation.  String manipulation is so much easier in assembly than it is in C.  Even code can be considered data, and programs can be made self modifying (for a quick permenant change in the program flow that only occures every 1200th iteration or so) to avoid needless if-then-else checks (at each iteration).  Function calls do not need to push every passed value into the stack; and they also don't need to pop the return value off the stack, which can save a butt-ton of time when when checking for an error: simply "GOTO if carry-flag is set" "error-handler routine" which looks like

--- Code: ---
--- End code ---

....
maybe one day I should get back into it...
Is it just me, or is the common consensus among assembly programmers to eschew OOP?

-t.

ps: did anyone mind the ramble?

ahri:
The books i'm talking about don't disscuss any assemblers, just chip archetecture and instructions. If he wants to learn how to use a specific assembler, he'll have to look else where. No matter what assember he goes with, he'll need the information in these books like how to use the registers, stack, protected mode, the different memory models, etc. Its general information that applies to all assemblers.

ahri:
btw, these books don't show you how to acctually write anything. There is souce code, but not a whole lot until the third volume which is dedicated to OS writing.

There are plenty of tutorials on the net that explain how to use various assemblers and how to write and assemble programs.

Navigation

[0] Message Index

[*] Previous page