public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iverbin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64412] [regression] ICE in offload compiler: in extract_insn, at recog.c:2327
Date: Thu, 08 Jan 2015 16:04:00 -0000	[thread overview]
Message-ID: <bug-64412-4-M4j8n65zjC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64412-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64412

--- Comment #19 from iverbin at gcc dot gnu.org ---
(In reply to iverbin from comment #18)
> It seems that the problem with offload is that -fPIC option is passed to the
> offload compiler, but not passed to the host compiler. If I add -fPIC to the
> host compiler as well, everything is ok.
> 
> I don't know how -fPIC option affects IR before streaming out,
> -fdump-tree-optimized are identical for pic/nonpic cases, but
> .gnu.offload_lto_.decls sections are different. However debug_tree
> (vnode->decl) for "G" in ipa_write_summaries are identical for pic/nonpic
> cases.
> 
> So, the question is, how to figure out what is different in G's declaration
> in IR, and how it can affect further expansion?

The regression is caused by LTO streaming of TARGET_OPTIMIZE_NODE:
https://gcc.gnu.org/ml/gcc-patches/2015-01/msg00376.html


  parent reply	other threads:[~2015-01-08 16:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 12:29 [Bug lto/64412] New: " iverbin at gcc dot gnu.org
2014-12-26 19:17 ` [Bug lto/64412] " hjl.tools at gmail dot com
2014-12-26 19:35 ` iverbin at gcc dot gnu.org
2014-12-27 15:21 ` [Bug target/64412] " hjl.tools at gmail dot com
2014-12-29 16:57 ` iverbin at gcc dot gnu.org
2014-12-29 16:57 ` iverbin at gcc dot gnu.org
2014-12-29 16:58 ` iverbin at gcc dot gnu.org
2014-12-29 18:10 ` hjl.tools at gmail dot com
2014-12-29 19:27 ` hjl.tools at gmail dot com
2014-12-29 19:28 ` hjl.tools at gmail dot com
2014-12-29 20:33 ` iverbin at gcc dot gnu.org
2014-12-29 20:33 ` iverbin at gcc dot gnu.org
2014-12-29 22:06 ` hjl.tools at gmail dot com
2014-12-30 13:09 ` [Bug middle-end/64412] " ubizjak at gmail dot com
2014-12-30 13:26 ` hjl.tools at gmail dot com
2014-12-30 14:35 ` ubizjak at gmail dot com
2014-12-30 15:12 ` hjl.tools at gmail dot com
2014-12-30 15:32 ` ubizjak at gmail dot com
2014-12-31 12:42 ` iverbin at gcc dot gnu.org
2015-01-08 16:04 ` iverbin at gcc dot gnu.org [this message]
2015-01-08 16:09 ` jakub at gcc dot gnu.org
2015-01-09 21:38 ` jakub at gcc dot gnu.org
2015-01-09 21:51 ` jakub 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-64412-4-M4j8n65zjC@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).