http://nostarch.com/assembly2.htm

Also, there's a related website:
http://homepage.mac.com/randyhyde/webster.cs.ucr.edu/index.html

The author makes an assembler called HLA (High Level Assembler) to make the transition to Assembly easier if you already have a language or two under your belt.

Also, probably outdated, but...
http://win32assembly.online.fr/tutorials.html

>>124
Looks great! Thanks a bunch.

>>123
Assembly is not a language. I'm trying to learn functional, hurr durr. Oh wait, that's not a language either. Imperative? Object-oriented? Nope, not languages either. (Get the analogy?)
Did you mean: x86 assembly
Did you mean: PowerPC assembly
Did you mean: Z80 assembly
Did you mean: .net assembly (lol, totally different)

>>185
I'm not sure it matters in this case. Intel processors are so common that most books or tutorials are going to focus on Intel assembly. Learning assembly for other processors would probably require getting the instruction manuals from the respective vendors. If OP does that without some general background in assembly programming, it could cause a big headache.

I could have sworn there was another post down here a week or so ago... Was it removed for some reason?

I remember it too. Weird.

>>193
It's the Rapture. It started early.

Why?

Are you building an emulator or something?

Why do you need to learn assembly?

>>202
Maybe OP is trying to optimize something, or perhaps just wants to learn for entertainment value.

I rather write system calls directly in assembly, optionally with an alternate implementation in C for portability.

Last time I had to do this was when I was porting a C library to Linux.

>>205
I'm curious about this. Wouldn't the general speed advances in hardware compensate for any latency for a system call in C? Do you just use assembly on the system call, or is it just a smaller part of a larger optimization task?

>>207
I didn't really care about optimisation in terms of speed, but size did concern me. I used assembly for program startup and system calls including exit. I also had to write a memory allocator, which required a couple more system calls but was otherwise written in plain C (which was easily the most difficult part of the porting job).

But overall using assembly was an easy way to do the port to Linux on x86_64 as the application did not use syscall and I had to write the "glue code" to the kernel by hand anyway. Very little code was needed because the calling conventions are awesome on this platform. C function calls and system calls are almost exactly the same, you just need to know the system call numbers.

/usr/include/x86_64-linux-gnu/asm/unistd_64.h <- they're all there ( sudo apt-get install linux-libc-dev )

Assembly Language Step-by-Step - Programming with Linux, 3rd Edition

>>125
She's in my unit. no joke.

>>270
Anyhting interesting you could share with us?

Why are pictures suddenly missing from this thread?

>>278
It seems to have happened on a lot of our lesser-used boards. I think it was in November. Possibly the files were accidentally deleted from the physical server by an external process.