Ping
On Fri, Nov 15, 2013 at 7:45 PM, Andrey Turetskiy
wrote:
> Let's suppose, we are going to run target gcc driver from lto-wrapper.
> How could a list of offload targets be passed there from option
> parser?
> In my opinion, the simpliest way to do it is to use environment
Jakub Jelinek wrote:
> On Fri, Nov 08, 2013 at 06:26:53PM +0400, Andrey Turetskiy wrote:
>> Thanks.
>> And a few questions about compiler options:
>> 1) You've mentioned two options for offloading:
>> -foffload-target= - to specify targets for offloading
>>
ht, that options for different targets should be
stored in different sections in fat object file, and than lto frontend
should read theese options and run target compilation with them?
On Thu, Nov 7, 2013 at 7:42 PM, Jakub Jelinek wrote:
> On Thu, Nov 07, 2013 at 07:36:06PM +0400, Andrey Ture
for mic and ptx.
--
Best regards,
Andrey Turetskiy
Ping
On Thu, Oct 31, 2013 at 7:42 PM, Andrey Turetskiy
wrote:
> Let's check my understanding:
> 1) We can configure gcc with, say, --offload-target=mic,ptx. It means
> that after build and install we have 3 compilers: for host, for mic
> and for ptx. In general case, the n
n like -foffload-target-x86_64-k1om-linux= if offload target hasn't been set during configuration?
On Tue, Oct 29, 2013 at 1:49 PM, Jakub Jelinek wrote:
> On Tue, Oct 29, 2013 at 01:33:17PM +0400, Andrey Turetskiy wrote:
>> I wonder how compiler is going to choose which target binaries sho
variables or paths will be set during compiler
configuration?
--
Best regards,
Andrey Turetskiy
