* Re: mixing .o architectures in a link
[not found] ` <199801231846.KAA08261.cygnus.bfd@canuck.cygnus.com>
@ 1998-01-23 15:00 ` Richard Henderson
0 siblings, 0 replies; only message in thread
From: Richard Henderson @ 1998-01-23 15:00 UTC (permalink / raw)
To: bfd
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~
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1998-01-23 15:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <34C8C15B.6EB40B96@cygnus.com>
[not found] ` <199801231846.KAA08261.cygnus.bfd@canuck.cygnus.com>
1998-01-23 15:00 ` mixing .o architectures in a link Richard Henderson
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).