public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/108511] [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 since r13-5285-g106f99406312d7ed
Date: Sun, 29 Jan 2023 00:01:08 +0000	[thread overview]
Message-ID: <bug-108511-4-1OXKHSYmcI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108511-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
The function is used to discard early summaries that will lead to external
calls. This saves some memory allocations.

At this stage we have identified prevailing symbols and they are first in the
next_sharing_asm_name lists.  So the code looks it up and it ices because there
is an external reference from one unit while previaling symbol is not public.
It happens with -r only since there we do not have resolution info.

Relaxing the assert to TREE_PUBLIC || DECL_EXTERNAL is safe and I guess easiest
way to get around.

  parent reply	other threads:[~2023-01-29  0:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  8:36 [Bug ipa/108511] New: [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 ro at gcc dot gnu.org
2023-01-24  8:36 ` [Bug ipa/108511] " ro at gcc dot gnu.org
2023-01-25  9:19 ` [Bug ipa/108511] [13 regression] ICE in possibly_call_in_translation_unit_p, at cgraph.cc:4184 since r13-5285-g106f99406312d7ed marxin at gcc dot gnu.org
2023-01-25  9:20 ` marxin at gcc dot gnu.org
2023-01-25 10:02 ` rguenth at gcc dot gnu.org
2023-01-25 10:30 ` marxin at gcc dot gnu.org
2023-01-25 12:07 ` rguenth at gcc dot gnu.org
2023-01-25 12:08 ` rguenth at gcc dot gnu.org
2023-01-29  0:01 ` hubicka at gcc dot gnu.org [this message]
2023-01-30  8:35 ` cvs-commit at gcc dot gnu.org
2023-01-30  8:35 ` rguenth 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-108511-4-1OXKHSYmcI@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).