From: Latchesar Ionkov <lucho@ionkov.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8a: getting the address of a label
Date: Mon, 29 Dec 2003 18:03:25 -0500 [thread overview]
Message-ID: <20031229230325.GA18194@ionkov.net> (raw)
In-Reply-To: <002f01c3ce3d$28079ba0$8201a8c0@cc77109e>
On Tue, Dec 30, 2003 at 05:54:10AM +1100, Bruce Ellis said:
> you can do this with the current ?a and ?l.
> just go crazy working out what the TEXT
> directive actually does. there is no need
> for it to be only used at the beginning of
> a function.
Is there any guarantee that the TEXT symbols will be laid out in the order
they appear in the file?
Also, if I remember correctly there are some checks
if PUSH/POP instructions are balanced (which I currently disabled). I am
sure that making some labels TEXT directives will break it even further ...
Thanks,
Lucho
>
> brucee
> ----- Original Message -----
> From: "Latchesar Ionkov" <lucho@ionkov.net>
> To: <9fans@cse.psu.edu>
> Sent: Tuesday, December 30, 2003 1:42 AM
> Subject: [9fans] 8a: getting the address of a label
>
>
> > Hi,
> >
> > I am still playing with the gcc port ...
> >
> > It would be very helpful, if Plan9 assembler and loader allow getting the
> > addresses of the labels. The exception handling code is messy enough even
> > without me trying to avoid using label addresses :( Also it would be useful
> > for better implementation of the switch statement, as well as some gcc
> > specific features like __label__ variables.
> >
> > Is there a chance that a patch that implements that will be accepted?
> >
> > Thanks,
> > Lucho
next prev parent reply other threads:[~2003-12-29 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 14:42 Latchesar Ionkov
2003-12-29 16:32 ` David Presotto
2003-12-29 18:54 ` Bruce Ellis
2003-12-29 23:03 ` Latchesar Ionkov [this message]
2003-12-30 1:59 ` David Presotto
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=20031229230325.GA18194@ionkov.net \
--to=lucho@ionkov.net \
--cc=9fans@cse.psu.edu \
/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).