Den Sat, 7 Sep 2013 16:34:40 -0400
skrev [pocl-devel] Triples, targets, cpus, and features... and HOST vs.
TARGET:

> To make things work, I freely used @HOST_* variables everywhere. I
> see that pocl makes some effort to use @TARGET_* variables in some
> places, but this was not done consistently, so I didn't try a correct
> solution here. I assume that the basic idea is that pocl is
> configured to produce code for HOST as well as (potentially) one
> additional device TARGET. While the host properties should be
> autodetected, the target properties probably need to be defined
> manually. I do not understand where this distinction is made,
> presumably at run time. Or is this a configuration time decision? If
> so, where is the decision made?

The confusion here arises from the device types where target==host,
i.e. the basic and pthreads devices. For these two, we probably should
use the HOST settings, unless we want to change calling conventions,
ABIs, or something in the kernels. Which we might want to do if we can
get some benefit out of it. Or perhaps when using SPIR. 

In the case of a heterogenous setup, the device driver should set all
the necessary TARGET flags, parts of this happens in configure.ac.

Currently, there is an implicit assumption, that any given pocl
installation has maximally one heterogenous target device. Which
assumption probably has left a few undocumented short-cuts in the
usage of TARGET flags at some places.

Yeah, its a mess :)


kalle

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel

Reply via email to