I'm curious - what is the use case for the old behaviour? AFAICT if the user sets `Enable OpenMP support` `OFF` they'll get a compiler that links against `libgomp` when `-fopenmp` is specified, but doesn't produce a useful openmp executable?
================ Comment at: test/OpenMP/linking_no_openmp.c:2 @@ +1,3 @@ +// Test the that the driver produces reasonable linker invocations with +// -fopenmp or -fopenmp|libgomp. +// REQUIRES: no_openmp ---------------- `-fopenmp=libgomp`? http://reviews.llvm.org/D9875 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
