Hello Bernd, On 28 Feb 17:21, Bernd Schmidt wrote: > For your use case, I'd imagine the offload compiler would be built > relatively normally as a full build with > "--enable-as-accelerator-for=x86_64-linux", which would install it > into locations where the host will eventually be able to find it. > Then the host compiler would be built with another new configure > option (as yet unimplemented in my patch set) > "--enable-offload-targets=mic,..." which would tell the host > compiler about the pre-built offload target compilers. On the ptx
I don't get this part of the plan. Where a host compiler will look for mkoffloads? E.g., first I configure/make/install the target gcc and corresponding mkoffload with the following options: --enable-accelerator=intelmic --enable-as-accelerator-for=x86_64-unknown-linux --prefix=/install_gcc/accel_intelmic Next I configure/make/install the host gcc with: --enable-accelerator=intelmic --prefix=/install_gcc/host Now if I manually copy mkoffload from target's install dir into one of the dirs in host's $COMPILER_PATH, then lto-wrapper finds it and everything works fine. E.g.: mkdir -p /install_gcc/host/libexec/gcc/x86_64-unknown-linux-gnu/accel/intelmic/ && cp /install_gcc/accel_intelmic/libexec/gcc/x86_64-unknown-linux/4.10.0/accel/x86_64-unknown-linux-gnu/mkoffload /install_gcc/host/libexec/gcc/x86_64-unknown-linux-gnu/accel/intelmic/ But what was your idea of how to tell host gcc about the path to mkoffload? Thanks, -- Ilya
