From: hpr <phpr@snafu.de>
To: Slack Traq <slacktraq@yahoo.com>, linux-assembly@vger.kernel.org
Subject: Re: Local Symbol Names
Date: Wed, 25 Jun 2003 19:06:06 +0100 [thread overview]
Message-ID: <200306251906.06250.phpr@snafu.de> (raw)
In-Reply-To: <20030625160958.46480.qmail@web11410.mail.yahoo.com>
Slack Traq am Mittwoch, 25. Juni 2003 17:09:
> --- S kris <kris_bs@hotmail.com> wrote:
> > Hi,
> >
> > In some of the assembly files, it's noticed that
> > Local Symbol Names have
> > been used that in the following way,
> >
> > ................
> > call 0f
> > 0: popl %eax
> > ................
> > The call is referring to immediately next statement.
> > Please help me in
> > finding out the significance of the above lines in
> > the assembly code.
> >
> > Thanks
> >
> > Kris
>
> Kris: the 'f' after the 'O' in the call statement is
> really unnecessary because the label begins in the
> next statement. Maybe is a call to a "far" function or
> label, but is quite obvious that 'O' is not such
nonsense! (assumed the code is from binutils' AS)
numeric labels can be redefined.
they are directionally referred, "f"orward or "b"ackword
the example fetches the address at label '0' to eax, which can be used to
supporting position independent code.
best,
hp
> label.
> I hope this will help you.
> Regards,
> Slack
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-assembly"
> in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Linux,Assembly,Forth: http://www.lxhp.in-berlin.de/index-lx.shtml en/de
pse, reply to << lxhp -at- lxhp -dot- in-berlin -dot- de >>
next prev parent reply other threads:[~2003-06-25 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 8:23 Local Symbol Names S kris
2003-06-25 16:09 ` Slack Traq
2003-06-25 18:06 ` hpr [this message]
2003-06-25 18:50 ` Jack Dennon
2003-06-25 19:44 ` Brian Raiter
2003-06-26 0:14 ` Jack Dennon
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=200306251906.06250.phpr@snafu.de \
--to=phpr@snafu.de \
--cc=linux-assembly@vger.kernel.org \
--cc=slacktraq@yahoo.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).