On Thu, Nov 05, 2015 at 10:47:15PM +0000, Joseph Myers wrote: > On Thu, 5 Nov 2015, Martin Jambor wrote: > > > libgomp plugin to be built. Because the plugin needs to use HSA > > run-time library, I have introduced options --with-hsa-runtime (and > > more precise --with-hsa-include and --with-hsa-lib) to help find it. > > New configure options should be documented in install.texi.
Right, I am about to commit the following patch to the branch (I have checked the make info output and it looks good). Thanks for the reminder. Martin [hsa] Document configuration changes 2015-11-09 Martin Jambor <mjam...@suse.cz> * install.texi (Configuration): Describe hsa --enable-offload-targets option, add description of --with-hsa-runtime, --with-hsa-runtime-include and --with-hsa-runtime-lib diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 57399ed..6984c40 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1982,6 +1982,22 @@ specifying paths @var{path1}, @dots{}, @var{pathN}. % @var{srcdir}/configure \ --enable-offload-target=i686-unknown-linux-gnu=/path/to/i686/compiler,x86_64-pc-linux-gnu @end smallexample + +If @samp{hsa} is specified as one of the targets, the compiler will be +built with support for HSA GPU accelerators. Because the same +compiler will emit the accelerator code, no path should be specified. + +@item --with-hsa-runtime=@var{pathname} +@itemx --with-hsa-runtime-include=@var{pathname} +@itemx --with-hsa-runtime-lib=@var{pathname} + +If you configure GCC with HSA offloading but do not have the HSA +run-time library installed in a standard location then you can +explicitely specify the directory where they are installed. The +@option{--with-hsa=@/@var{hsainstalldir}} option is a shorthand for +@option{--with-hsa-lib=@/@var{hsainstalldir}/lib} and +@option{--with-hsa-include=@/@var{hsainstalldir}/include}. + @end table @subheading Cross-Compiler-Specific Options