Hi! On Tue, 3 Sep 2013 19:18:01 +0400, "Michael V. Zolotukhin" <michael.v.zolotuk...@gmail.com> wrote: > > - collect all those target object files from the link, link them together > > using target compiler driver, and feed back the resulting binary > > or shared library into the host linking (some magic section in there) > Why do we need to feed the target binary back to the host linking? The > host program cannot directly call any routine from the target binary, so > IMHO there is no point in linking them together, they are just separate > executables.
The idea, as we discussed it at the GNU Tools Cauldron's Acceleration BoF, is that the host program (for at least some acceleration devices) will be responsible for loading the acceleration device's code to the device, using some support library that is specific to each acceleration device, and for that it is useful to have the the code readily accessible in the host program, and thus link it in as "data". > And the question about multi-target support here still remains open. Many questions are still open -- but I'm glad there is activity on this topic, and I'm sure we'll be able to converge with the designs we have or are currently developing. Grüße, Thomas
pgpUfVZnouAkr.pgp
Description: PGP signature
