https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64707
--- Comment #5 from vries at gcc dot gnu.org ---
Author: vries
Date: Fri Jan 23 12:53:55 2015
New Revision: 220037
URL: https://gcc.gnu.org/viewcvs?rev=220037&root=gcc&view=rev
Log:
Make fopenmp an LTO option
2015-01-23 Tom de Vries
PR l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64707
vries at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64707
--- Comment #4 from vries at gcc dot gnu.org ---
Created attachment 34535
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34535&action=edit
tentative patch, makes fopenmp an LTO option, adds lto-wrapper handling
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64707
--- Comment #3 from vries at gcc dot gnu.org ---
Created attachment 34515
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34515&action=edit
tentative patch, adding flag_ltrans || flag_wpa to the GOMP builtin guard
conditions
(In reply to Jak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64707
--- Comment #2 from Jakub Jelinek ---
Wouldn't it be better to just add || flag_ltrans || flag_wpa to the GOMP/GOACC
builtin guard conditions?
I mean, relying on global flags here when they are combined from many sources,
where some may be compil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64707
--- Comment #1 from vries at gcc dot gnu.org ---
Created attachment 34512
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34512&action=edit
tentative patch
