public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Tue, 20 Jan 2015 10:39:00 -0000	[thread overview]
Message-ID: <bug-64672-4-zjSbh8CNVO@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 #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, -fopenmp isn't marked LTO, so if not anything else, for consistency
-fopenacc should be handled similarly as -fopenmp.


  parent reply	other threads:[~2015-01-20 10:39 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 [this message]
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
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-zjSbh8CNVO@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).