This link helped me when I was learning about x86 on OpenBSD... http://www.phiral.net/openbsdasm.htm
I decided not to use the GCC __asm__ deal for various reasons that I don't remember. I think in particular.. I did not like the look at AT&T syntax vs. Intel syntax. I wrote an assembly version of AES, Serpent and Twofish algorithms using NASM under OpenBSD and everything worked. To me.. it seemed nice to be able to write a program in C that calls functions in a NASM created obj file. This seemed very portable and my code does indeed work under windows with only slight modifications. My project is here: http://asmaes.sourceforge.net/ ---- Tobias Ulmer <[EMAIL PROTECTED]> wrote: > On Fri, Jul 25, 2008 at 01:12:58PM +0000, Matthew Szudzik wrote: > > On Thu, Jul 24, 2008 at 07:16:55PM -0600, Philip Guenther wrote: > > > If you're just trying to learn the x86 instruction set, then why not > > > put your code in an __asm__() block inside a C program? That lets the > > > compiler do all the heavy lifting. > > > > Is there a man page that describes the __asm__ block? The gcc man page > > only describes how to turn it on or off, and since it's nonstandard C, > > it's not described in any of the standard reference books like K&R. > > > > > > http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gcc/Extended-Asm.html#Extended-Asm
