From: Parag Warudkar <kernel-stuff@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: Re: techniques used in assembly language programming.
Date: Fri, 17 Jun 2005 15:22:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20050617T171332-740@post.gmane.org> (raw)
In-Reply-To: 42B29EF5.4070906@globaledgesoft.com
krishna <krishna.c <at> globaledgesoft.com> writes:
>
> Hi All,
>
> Can any one tell me any sources to learn techniques in assembly language
> programming.
>
> Regards,
> Krishna Chaitanya
>
Assuming you want to learn assembly for x86 -
I have found it easier to first understand the machine and basics of low level
software/hardware interaction and then move on to learn assembly language -
machine organization and related basics are nicely covered in the
Book "Writing Great Code" by Randall Hyde who also has written a very thorough
and excellent book (freely downloadable from http://webster.cs.ucr.edu/) Art
of Assembly Language Programming.
HTH
Parag
prev parent reply other threads:[~2005-06-17 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 9:59 techniques used in assembly language programming krishna
2005-06-17 15:22 ` Parag Warudkar [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=loom.20050617T171332-740@post.gmane.org \
--to=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
/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