https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64672
--- Comment #18 from vries at gcc dot gnu.org --- (In reply to rguent...@suse.de from comment #15) > On Wed, 21 Jan 2015, vries at gcc dot gnu.org wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64672 > > > > --- Comment #14 from vries at gcc dot gnu.org --- > > (In reply to rguent...@suse.de from comment #13) > > > But I prever -fopenmp/-fopenacc as LTO > > > options. > > > > > > > What is the rationale for the preference ? > > Might be required for -fparallelize-loops or vectorization to work (not > sure)? > I'm not aware of any related problems there. Jakub, AFAIU, the last patch (makes fopenacc an LTO option, adds lto-wrapper handling) handles the objections you raised in PR64707 comment 2. Is the last patch ok, or do you still prefer the 'flag_ltrans || flag_wpa' one?