From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] which register is used as FP on the x86
Date: Sat, 26 Jun 2004 18:31:49 +0100 [thread overview]
Message-ID: <1c1777afc7d72d155cf0b95c13df7021@terzarima.net> (raw)
In-Reply-To: <f158dc6704062607275e56ba4e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 144 bytes --]
the function that owns them knows it creates them,
and can modify its behaviour accordingly, rather
than pushing the requirement everywhere.
[-- Attachment #2: Type: message/rfc822, Size: 2864 bytes --]
From: Latchesar Ionkov <lionkov@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] which register is used as FP on the x86
Date: Sat, 26 Jun 2004 10:27:53 -0400
Message-ID: <f158dc6704062607275e56ba4e@mail.gmail.com>
This approach doesn't work if the compiler supports variable length
arrays. Fortunately (or unfortunately, depending on your preferences)
the Plan9 compiler doesn't suport them.
Thanks,
Lucho
On Fri, 25 Jun 2004 18:53:48 +0100, rog@vitanuova.com <rog@vitanuova.com> wrote:
>
> no register is dedicated as a frame pointer.
>
> if you know the PC, you can find out the FP from the SP.
>
>
next prev parent reply other threads:[~2004-06-26 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 17:30 ron minnich
2004-06-25 17:53 ` rog
2004-06-26 11:56 ` Andrew Lynch
2004-06-26 12:35 ` Latchesar Ionkov
2004-06-26 12:35 ` Charles Forsyth
2004-06-26 14:27 ` Latchesar Ionkov
2004-06-26 17:31 ` Charles Forsyth [this message]
2004-07-03 7:17 ` [9fans] cpuserver: dhcp for authsrv, rio, users, ssh, factotum, pull Stephen Wynne
2004-07-03 16:37 ` [9fans] andrey mirtchovski
2004-07-05 4:06 ` [9fans] Stephen Wynne
2004-07-05 17:23 ` [9fans] andrey mirtchovski
2004-07-05 20:33 ` [9fans] Eric Grosse
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=1c1777afc7d72d155cf0b95c13df7021@terzarima.net \
--to=forsyth@terzarima.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).