From: dh <dh@icbook.com.ua>
To: Assembly Linux <linux-assembly@vger.kernel.org>
Subject: Re:variables & How interrupts work
Date: Fri, 23 Aug 2002 14:52:19 +0200 [thread overview]
Message-ID: <3D663003.7800E652@icbook.com.ua> (raw)
Hi all!
> Hi all,
and Hi RCS!
>
> I need some help to understand how interrupts work on Intel.
Intel can help you to understand how interrupts work on x86 :)
http://developer.intel.com/design/PentiumIII/manuals/
> For example, how do I print a character in the screen?
> Wich register must contain the character for that? Is "int 10h" the correct
> interrupt for that?
Yes, int 10 is correct interrupt for that.
For more information, please, input in google.com string - helppc,
download this program and just read.
> Hi all,
>
> Can anyone explain me how global and local variables from C are treated in
>assembler?
Many people know how it make, but explain this for you...
It's a very long story.
> Is that write that local variables are storage in the stack?
Not, it isn't write :)
Good buy all!
Khmara Dmitro
engineer, IC Book Lab
dh@icbook.com.ua
www.icbook.com.ua
reply other threads:[~2002-08-23 12:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D663003.7800E652@icbook.com.ua \
--to=dh@icbook.com.ua \
--cc=linux-assembly@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;
as well as URLs for NNTP newsgroup(s).