public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108984] [13 Regression] LTO bootstrap causes testsuite ICE
Date: Wed, 01 Mar 2023 13:05:50 +0000 [thread overview]
Message-ID: <bug-108984-4-WGuRzpCA8J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108984-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108984
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
So there's interesting IPA summary on gen_rtx_CONST_INT.constprop/2274667
find_slot_with_hash.constprop/2274668 function not considered for inlining
freq:0.49 loop depth: 0 size: 6 time: 15 callee size:41 stack: 0
predicate: (op1,((unsigned long) #),(# + 64) > 128)
op1 is compile time invariant
op1 points to local or readonly memory
op3 is compile time invariant
it looks like the parameter removal does not adjust the parameter number?
for the constprop clone the first parameter is constant VOIDmode (0), but
the second is unknown. Not sure what '#' and op1 refer to for the
predicate though. The above is from the IPA inline dump at WPA time.
Note I do not see redirect_to_unreachable being called with e->callee->m_uid ==
2274668 during WPA. The function is called a lot, but too many times to
watch all of them (it's not called at LTRANS time at all).
next prev parent reply other threads:[~2023-03-01 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 10:25 [Bug target/108984] New: " rguenth at gcc dot gnu.org
2023-03-01 10:44 ` [Bug target/108984] " rguenth at gcc dot gnu.org
2023-03-01 12:14 ` rguenth at gcc dot gnu.org
2023-03-01 12:21 ` jakub at gcc dot gnu.org
2023-03-01 13:05 ` rguenth at gcc dot gnu.org [this message]
2023-03-01 13:23 ` rguenth at gcc dot gnu.org
2023-03-01 13:34 ` rguenth at gcc dot gnu.org
2023-03-01 13:45 ` jakub at gcc dot gnu.org
2023-03-01 14:01 ` rguenth at gcc dot gnu.org
2023-03-02 7:25 ` 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-108984-4-WGuRzpCA8J@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).