public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict
Date: Tue, 22 Sep 2020 19:57:49 +0000	[thread overview]
Message-ID: <bug-97159-4-cxv7ISDlB6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97159-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jan Hubicka <hubicka at ucw dot cz> ---
Recursion is handled in normal compilation (we analyze the function and
while hitting the recursive call we skip the summary). I suppose here
the problem is missing LTO and offloading. 

With LTO lto summaries (that include types) are streamed out while they
are turned into non-lto summaries at ltrans time.  We need to do similar
thing with offload.

Honza

  parent reply	other threads:[~2020-09-22 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  9:34 [Bug tree-optimization/97159] New: " vries at gcc dot gnu.org
2020-09-22  9:38 ` [Bug tree-optimization/97159] " vries at gcc dot gnu.org
2020-09-22  9:47 ` vries at gcc dot gnu.org
2020-09-22 10:51 ` [Bug tree-optimization/97159] [11 Regression] " rguenth at gcc dot gnu.org
2020-09-22 19:57   ` Jan Hubicka
2020-09-22 19:57 ` hubicka at ucw dot cz [this message]
2020-10-05  7:17 ` vries at gcc dot gnu.org
2020-10-06  8:18 ` 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-97159-4-cxv7ISDlB6@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).