From: "Frank Ch. Eigler" <fche@redhat.com>
To: John Healy <jhealy@redhat.com>
Cc: cgen@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: Changes To Fixup Saving, Restoring and Swapping
Date: Thu, 05 Jul 2001 09:57:00 -0000 [thread overview]
Message-ID: <20010705125702.D30453@redhat.com> (raw)
In-Reply-To: <3B449A0D.33C3DCCA@redhat.com>
Hi -
jhealy wrote:
: A port I'm working on requires packing a set of instructions (two at
: this point, more later) into a vliw word. In order to be able to
: handle more than two instructions at a time during assembly, an
: enhancement to the gas_cgen_[save/restore/swap]_fixups mechanism is
: required. [...]
All okay, except for:
: [...] Just in case it might be of
: use, I've also added a little extra feature that allows for the current
: fixups to be either kept or cleared when stored and for a set of stored
: fixups to be either kept or cleared when restored.
I would prefer not to have this extension in the code, unless your current
internal port has use for it, or unless you can make a more persuasive
argument for it than "just in case".
: I threw some documentation in too. [and tested on m32r]
Thanks!
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7RJxeVZbdDOm/ZT0RAsz/AKCH1id0kVDdKAmHx2dWez4hoA23ewCePn8+
l/y/Z+aJm3Ltz9qclyMBCvM=
=f50m
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-07-05 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 9:47 John Healy
2001-07-05 9:57 ` Frank Ch. Eigler [this message]
2001-07-05 10:12 ` John Healy
2001-07-05 10:17 ` Frank Ch. Eigler
2001-07-05 10:35 ` John Healy
2001-07-05 10:07 ` Doug Evans
2001-07-05 11:04 ` Greg McGary
2001-07-05 11:36 ` John Healy
[not found] ` <3B44A559.2E890F58.cygnus.local.cgen@redhat.com>
2001-07-06 12:11 ` John Healy
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=20010705125702.D30453@redhat.com \
--to=fche@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=jhealy@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).