On Thu, Dec 18, 2014 at 01:02:22PM +0100, Jakub Jelinek wrote:
> On Thu, Dec 18, 2014 at 12:38:53PM +0100, Jakub Jelinek wrote:
> > So, is what is on the gomp-4_0-branch now all that you'd like to merge to
> > trunk now? Has it been tested on nvptx? I guess we should test it with
> > XeonPhi offloading too to make sure it doesn't break.
> > And then you or together with your coworkers should write the summary
> > ChangeLogs (i.e. what changed compared to trunk in a single giant entry
> > for each ChangeLog file as opposed to many ChangeLog.gomp change entries).
>
> Also, it would be nice to update wiki/Offloading to give details on all the
> steps how to configure nvptx offloading (how to grab nvptx-newlib,
> nvptx-tools, how to configure nvptx-none compiler, in what order to build
> those etc.).
FYI, just tried to build gomp-4_0-branch with:
../configure --build=x86_64-intelmicemul-linux-gnu
--host=x86_64-intelmicemul-linux-gnu --target=x86_64-intelmicemul-linux-gnu
--enable-as-accelerator-for=x86_64-pc-linux-gnu --disable-bootstrap
make -j16
and the build failed with:
../../gcc/builtins.c: In function ‘rtx_def* expand_builtin_acc_on_device(tree,
rtx)’:
../../gcc/builtins.c:5904:17: error: ‘ACCEL_COMPILER_acc_device’ was not
declared in this scope
v2 = GEN_INT (ACCEL_COMPILER_acc_device);
^
../../gcc/rtl.h:3186:51: note: in definition of macro ‘GEN_INT’
#define GEN_INT(N) gen_rtx_CONST_INT (VOIDmode, (N))
^
Where is ACCEL_COMPILER_acc_device macro supposed to be defined?
Jakub
