On Fri, 14 Aug 2015, Thomas Schwinge wrote:

> This function »generate[s] a C source file containing a constructor call
> to GOMP_set_offload_targets [...], and adds that as an infile«.  This
> "basically" works ;-) -- but really only for C source code, and for C++
> and Fortran it fails if there are command-line options used that conflict
> with the C compilation of add-omp-infile, such as (from a libgomp
> testsuite run): for C++: -std=c++11, -fno-extern-tls-init, or for
> Fortran: -fcray-pointer, -fintrinsic-modules-path.  Any suggestion about
> how to overcome that?

I suppose you need to use the option-handling information about which 
options are for which languages to filter out any options that aren't 
valid for C or Common.

-- 
Joseph S. Myers
joseph@codesourcery.com