From: Brian Raiter <breadbox@muppetlabs.com>
To: linux-assembly@vger.kernel.org
Subject: Re: 32-bit assembler::how to initialize segment registers
Date: Tue, 19 Oct 2004 08:07:46 -0700 [thread overview]
Message-ID: <16757.11714.516046.996092@eidolon.muppetlabs.com> (raw)
In-Reply-To: <56005.10.0.0.20.1098162741.squirrel@mail.cusat.ac.in>
> am making 32-bit
> assembler as project in c under linux platform.
> my problem is how my assembler should
> initialize the segment registers.
Assuming the output of your assembler is a Linux object file, then the
segment registers are not your responsibility. Linux sets up the
segment registers before the user's code is called. If the programmer
wants to do something bizarre and/or clever with segments, then it's
their responsiblity.
b
next prev parent reply other threads:[~2004-10-19 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 5:12 32-bit assembler::how to initialize segment registers san
2004-10-19 5:40 ` zebarbuc
2004-10-19 14:47 ` Muthu
2004-10-20 1:57 ` Daniel R. Blair
2004-10-20 8:24 ` Fred Marmond
2004-10-19 15:07 ` Brian Raiter [this message]
2004-10-19 20:09 ` HLA v1.71 is now available Randall Hyde
2004-10-19 20:30 ` Claudio Fontana
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=16757.11714.516046.996092@eidolon.muppetlabs.com \
--to=breadbox@muppetlabs.com \
--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).