From: Andy Walker <ja_walker@earthlink.net>
To: gcc@gcc.gnu.org
Subject: Synthetic register related: consequences of changing Frame layout.
Date: Sat, 04 Jan 2003 07:04:00 -0000 [thread overview]
Message-ID: <E18UiLf-0006bo-00@albatross.prod.itd.earthlink.net> (raw)
I am thinking about changing the frame layout for i386, but only when
Synthetic registers are used.
In particular, I want to align the hard-frame-pointer on a 32 byte boundary.
My instinct is that I will have to copy the old pc and old frame pointer to
new locations to correspond to the modified hard-frame-pointer. I will have
to hunt down the place that points to the arguments above the
hard-frame-pointer and adjust them so that the arguments are correctly found.
The saved registers will go below the hard-frame-pointer and the Synthetic
registers, and I will have to modify the register save/restore processes to
match the new layout.
What else am I likely to break in the process?
Andy
next reply other threads:[~2003-01-04 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 7:04 Andy Walker [this message]
2003-01-04 17:55 ` Denis Chertykov
2003-01-05 5:44 ` Andy Walker
2003-01-05 11:42 Robert Dewar
2003-01-06 5:01 ` Andy Walker
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=E18UiLf-0006bo-00@albatross.prod.itd.earthlink.net \
--to=ja_walker@earthlink.net \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).