public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/64672] ICEs in libgomp.oacc-fortran when using the '-g -flto' options in the test suite.
Date: Fri, 23 Jan 2015 00:02:00 -0000 [thread overview]
Message-ID: <bug-64672-4-rgO1S85NHy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64672-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64672
--- Comment #18 from vries at gcc dot gnu.org ---
(In reply to rguenther@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 rguenther@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?
next prev parent reply other threads:[~2015-01-23 0:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 15:44 [Bug libgomp/64672] New: " dominiq at lps dot ens.fr
2015-01-19 15:49 ` [Bug libgomp/64672] " dominiq at lps dot ens.fr
2015-01-19 22:40 ` howarth at bromo dot med.uc.edu
2015-01-19 22:41 ` howarth at bromo dot med.uc.edu
2015-01-19 22:54 ` dominiq at lps dot ens.fr
2015-01-20 8:18 ` rguenth at gcc dot gnu.org
2015-01-20 10:28 ` vries at gcc dot gnu.org
2015-01-20 10:39 ` jakub at gcc dot gnu.org
2015-01-20 12:17 ` dominiq at lps dot ens.fr
2015-01-20 12:26 ` vries at gcc dot gnu.org
2015-01-20 18:27 ` dominiq at lps dot ens.fr
2015-01-21 11:27 ` vries at gcc dot gnu.org
2015-01-21 12:48 ` vries at gcc dot gnu.org
2015-01-21 12:51 ` rguenther at suse dot de
2015-01-21 13:06 ` vries at gcc dot gnu.org
2015-01-21 13:17 ` rguenther at suse dot de
2015-01-22 22:10 ` vries at gcc dot gnu.org
2015-01-22 23:03 ` vries at gcc dot gnu.org
2015-01-23 0:02 ` vries at gcc dot gnu.org [this message]
2015-01-23 0:04 ` jakub at gcc dot gnu.org
2015-01-23 9:13 ` rguenther at suse dot de
2015-01-23 10:12 ` vries at gcc dot gnu.org
2015-01-23 12:55 ` vries at gcc dot gnu.org
2015-01-23 15:51 ` [Bug lto/64672] " vries at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-64672-4-rgO1S85NHy@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).