linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Kotler <fbkotler@comcast.net>
To: Only OpenSource <onlyopensource@gmail.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: which assembler to use : newbie query
Date: Tue, 01 Aug 2006 18:17:48 -0400	[thread overview]
Message-ID: <44CFD30C.60900@comcast.net> (raw)
In-Reply-To: <a779d4420607310812w3be15123ja4902cb19bdaea3b@mail.gmail.com>

Only OpenSource wrote:
> Hello all
> 
> I want to learn assembly language properly so that I can understand
> FreeBSD assembly code.
> Which assembler do I need to use : as or nasm.

Yes. :)

Here's something I just posted elsewhere - not really the same question, 
but maybe close enough...

--------------------------

MQ wrote:

 > Noway2 wrote:
 >
 >> Sam wrote:
 >>
 >>>> Can anyone recommend a tutorial on NASM syntax (other than Dr. Paul
 >>>> Carter's ?) Or any assembler book using NASM syntax? I'm shifting from
 >>>> gas to nasm -- that's why.
 >>>>
 >>>> thanks.
 >>>
 >>>
 >>> I'm new to assembler and thought I'd learn (g)as since GNU puts out a
 >>> ton of other development tools. Why are you shifting to NASM? Since I'm
 >>> fresh into learning assembler I might want to make the shift also...
 >>
 >>
 >> The fact that the gnu assembler syntax is awful probably has a lot to
 >> do with it.
 >
 >
 >
 > yes, gas uses AT&T syntax, which is a pile of steaming manure...


Recent versions of Gas, perhaps not available for djgpp(?), have an 
".intel_syntax noprefix" switch, which produces *less* steam.

It wasn't added for gcc's convenience, so the argument that Gas is "only 
fit for gcc's output" is no longer true. (although it *was*, at one time!!!)

I'm one of Nasm's biggest fans, and I don't think you'll go far wrong 
choosing Nasm... *but*... Nasm doesn't have 64-bit support, and isn't 
likely to, soon. Gas (and Fasm and Yasm) do. This might influence your 
decision!

Why not become "bilingual"? I can't *write* anything in Gas without 
making a lot of syntax errors, but I can read it and figure out what 
it's doing... usually. Pretty handy to have *some* familiarity with 
both! (Fasm and Yasm are similar enough to Nasm that they almost come 
free... couple subtleties...)

As far as a tutorial... other than Dr. Carter's... Maybe:

http://docs.cs.up.ac.za/programming/asm/derick_tut/

http://www.leto.net/writing/nasm.txt

http://www.rawcode.org/

This last is brand new - mostly in Italian (except for the code, which 
is in Intel), but being translated to English "as we speak" - and the 
guy is looking for help!

Seems to me there are a couple more - I can't find links right now - 
none of 'em as extensive as Dr. Carter's...

http://www.linuxassembly.org

is a good place to look for info and links...

Best,
Frank

P.S. For BSD, add the BSD Developer's Handbook, chapter... 17, I think? 
You can find it. *Very* good!



      parent reply	other threads:[~2006-08-01 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 15:12 which assembler to use : newbie query Only OpenSource
2006-07-31 17:01 ` leslie.polzer
2006-07-31 18:05 ` Ricardo Nabinger Sanchez
2006-07-31 20:01 ` Robert Plantz
2006-08-01  7:18   ` Hendrik Visage
2006-08-01  8:49     ` leslie.polzer
2006-08-02 14:43       ` Robert Plantz
2006-08-03  7:55         ` Maciej Hrebien
2006-08-01 22:17 ` Frank Kotler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44CFD30C.60900@comcast.net \
    --to=fbkotler@comcast.net \
    --cc=linux-assembly@vger.kernel.org \
    --cc=onlyopensource@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).