From: rth@cygnus.com (Richard Henderson)
To: bfd@cygnus.com
Subject: Re: mixing .o architectures in a link
Date: Fri, 23 Jan 1998 15:00:00 -0000 [thread overview]
Message-ID: <6ab6tu$glj$1@dot.cygnus.com> (raw)
In-Reply-To: <199801231846.KAA08261.cygnus.bfd@canuck.cygnus.com>
In article <199801231846.KAA08261.cygnus.bfd@canuck.cygnus.com>,
Doug Evans <devans@cygnus.com> wrote:
> The concept is that code and data for the two VUs is loaded into
> the 5900 address space for subsequent transfer to the VUs under
> explicit control of the 59 program. (It may make sense to put
> the VU text in the 59 text segment as it should be read-only.
> For VU data, the same arguments could be made.)
This may be less automatic than you like, but the way I would do
it with existing tools is to link the VU program by itself, then
create a MIPS object with a section containing the finished VU
program via objcopy trickery.
But that may just be too gross for the Product you are trying to
produce...
r~
parent reply other threads:[~1998-01-23 15:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <199801231846.KAA08261.cygnus.bfd@canuck.cygnus.com>]
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='6ab6tu$glj$1@dot.cygnus.com' \
--to=rth@cygnus.com \
--cc=bfd@cygnus.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).