public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: "Michael V. Zolotukhin" <michael.v.zolotukhin@gmail.com>
Cc: Ilya Verbin <iverbin@gmail.com>,
	Richard Biener	<richard.guenther@gmail.com>,
	Uday Khedker <uday@cse.iitb.ac.in>,	<hubicka@ucw.cz>,
	<rth@redhat.com>, <kirill.yukhin@gmail.com>,	<gcc@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>
Subject: Re: Questions about LTO infrastructure and pragma omp target
Date: Tue, 03 Sep 2013 17:39:00 -0000	[thread overview]
Message-ID: <87ioyhhkk9.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20130903151801.GE43295@msticlxl57.ims.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

Hi!

On Tue, 3 Sep 2013 19:18:01 +0400, "Michael V. Zolotukhin" <michael.v.zolotukhin@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

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2013-09-03 17:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 13:44 Ilya Verbin
2013-08-15 15:00 ` Jakub Jelinek
2013-08-15 19:19   ` Richard Biener
2013-08-23 13:15     ` Ilya Verbin
2013-08-23 14:38       ` Jakub Jelinek
2013-08-28  9:59         ` Basile Starynkevitch
2013-08-23 15:05       ` Richard Biener
2013-08-23 15:06         ` Jakub Jelinek
2013-08-25 22:36           ` Ilya Verbin
2013-08-26  7:32             ` Jakub Jelinek
2013-09-03 14:00               ` Michael V. Zolotukhin
2013-09-03 14:19                 ` Jakub Jelinek
2013-09-03 15:18                   ` Michael V. Zolotukhin
2013-09-03 17:39                     ` Thomas Schwinge [this message]
2013-09-03 18:30                       ` Michael V. Zolotukhin
2013-09-03 18:54                         ` Jakub Jelinek
2013-09-03 19:09                           ` Michael V. Zolotukhin
2013-09-16 17:14         ` Ilya Verbin
2013-09-17  8:12           ` Richard Biener
2013-09-17 11:31             ` Ilya Verbin
2013-09-17 11:54               ` Jakub Jelinek
2013-09-17 11:56               ` Richard Biener
2013-09-17 12:15                 ` Jakub Jelinek
2013-09-19 10:45                   ` Ilya Verbin
2013-09-19 10:50                     ` Jakub Jelinek

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=87ioyhhkk9.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=iverbin@gmail.com \
    --cc=jakub@redhat.com \
    --cc=kirill.yukhin@gmail.com \
    --cc=michael.v.zolotukhin@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=rth@redhat.com \
    --cc=uday@cse.iitb.ac.in \
    /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).