From: "Arun Vishwanathan" <arun.vishwanathan@nevisnetworks.com>
To: "Bill Cunningham" <billc_2@charter.net>, <binutils@sources.redhat.com>
Subject: RE: GAS
Date: Wed, 05 May 2004 14:09:00 -0000 [thread overview]
Message-ID: <36993D449C7FA647BF43568E0793AB3E4E3429@nevis_pune_xchg.pune.nevisnetworks.com> (raw)
No universal assembly language format. But it should not be difficult
to adapt to syntaxes once you learn one format. Intel one is probably
simpler so you can start with that.
This maybe a good links to start with if you are programming on Linux.
http://linuxassembly.org/
http://www.tldp.org/HOWTO/Assembly-HOWTO/
Regards,
-------------------------------------------------------------
"Only two things are infinite, the universe and human stupidity;
and i am not sure about the former"
-Albert Einstein
-------------------------------------------------------------
Arun Vishwanathan
> -----Original Message-----
> From: binutils-owner@sources.redhat.com [mailto:binutils-
> owner@sources.redhat.com] On Behalf Of Bill Cunningham
> Sent: Wednesday, May 05, 2004 7:19 PM
> To: binutils@sources.redhat.com
> Subject: GAS
>
> I all I just signed up to this list and I've been wanting to learn
> assembly as well as C. The GAS assembly format is what I want to learn
and
> Intel's IA-32 assembly language format. Is assembly language syntax
> different, or is there a universal assembly format I should learn?
>
> Bill
>
next reply other threads:[~2004-05-05 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 14:09 Arun Vishwanathan [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 9:11 Re[2]: GAS Stas Kiselev
2005-04-15 10:48 ` GAS Nick Clifton
2005-04-12 13:53 GAS Zagorodnev, Grigory
2005-04-14 9:00 ` GAS Nick Clifton
2005-04-05 7:52 Re[2]: GAS Zagorodnev, Grigory
2005-04-06 11:17 ` GAS Nick Clifton
2005-04-04 16:03 GAS Zagorodnev, Grigory
2005-04-04 14:51 GAS Stas Kiselev
2004-05-05 13:49 GAS Bill Cunningham
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=36993D449C7FA647BF43568E0793AB3E4E3429@nevis_pune_xchg.pune.nevisnetworks.com \
--to=arun.vishwanathan@nevisnetworks.com \
--cc=billc_2@charter.net \
--cc=binutils@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).