https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64672
--- Comment #11 from vries at gcc dot gnu.org --- (In reply to Dominique d'Humieres from comment #10) > > Perhaps for consistency, we should mark both fopenmp and fopenacc > > as LTO options? > > Not sure to understand. Is it not what the patch at > https://gcc.gnu.org/ml/gcc-patches/2014-11/msg00085.html does? > That patch marks _only_ fopenacc as LTO option. (In reply to vries from comment #9) > I verified this by adding -ftree-parallelize-loops=0, and found that indeed > support for omp builtins was dropped in lto1: > ... > (gdb) p builtin_info.decl[BUILT_IN_OMP_GET_THREAD_NUM] > $3 = (tree_node *) 0x0 > ... Using this information, I've managed to trigger a libgomp testsuite failure for fopenmp, filed as PR 64707: 'FAIL: libgomp.c/target-9.c with -ftree-parallelize-loops=0'.
