public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/106260] [10/11/12/13 Regression] ICE in initialize_node_lattices, at ipa-cp.cc:1289 since r8-1887-g0eaf0bfe94ff5a7c
Date: Wed, 13 Jul 2022 16:58:06 +0000	[thread overview]
Message-ID: <bug-106260-4-ogUSWQxA8g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106260-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> ---
IPA-CP is confused by seeing a local function which does not have any caller,
it expects that all such functions would be removed as unreachable.

The assert has been somewhat useful so I'd rather keep it but perhaps it should
not trigger when there is -fno-toplevel-reorder in place?

Of course, using both -fno-toplevel-reorder and -fwhole-program is a bit
strange .

Interestingly, the manual description of -fno-toplevel-reorder only says that
"unreferenced static variables are not removed" but does not say anything about
not removing static uncalled functions.

  parent reply	other threads:[~2022-07-13 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 18:58 [Bug c++/106260] New: [10/11/12/13 Regression] ICE in initialize_node_lattices, at ipa-cp.cc:1289 gscfq@t-online.de
2022-07-11 19:57 ` [Bug ipa/106260] [10/11/12/13 Regression] ICE in initialize_node_lattices, at ipa-cp.cc:1289 since r8-1887-g0eaf0bfe94ff5a7c marxin at gcc dot gnu.org
2022-07-11 21:05 ` pinskia at gcc dot gnu.org
2022-07-12  6:35 ` rguenth at gcc dot gnu.org
2022-07-13 16:58 ` jamborm at gcc dot gnu.org [this message]
2022-07-13 21:07 ` jamborm at gcc dot gnu.org
2023-07-07 10:43 ` [Bug ipa/106260] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-12-10  9:07 ` zsojka at seznam dot cz

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-106260-4-ogUSWQxA8g@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).