This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fwd: [RFC][gomp4] Offloading patches (2/3): Add tables generation

On 06/17/2014 08:20 PM, Ilya Verbin wrote:
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

Try using the same prefix for both.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]