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:23:51 +0000	[thread overview]
Message-ID: <bug-108984-4-uuhTcCWVcz@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 #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
But

void foo ();
int data[128];
static int bar (int i, int j)
{
  if (j > -64 && j < 64)
    return data[j+64];
  foo ();
}

int baz (int j)
{
  return bar (0, j);
}

seems to work fine with -O2 -fno-early-inlining -fipa-cp-clone, we create
a similar clone and have a similar inlining predicate.  But still the
predicate looks exactly the same whether we IPA CP or not ...

  calls:
    foo/3 function body not available
      freq:0.49 loop depth: 0 size: 1 time: 10 predicate: (op1,((unsigned int)
#),(# + 63) > 126)

But with IPA CP we get

  Parm map:  -5 0

I suspect -5 is for "removed" and 1 is mapped to 0.  But with the original
case we see

  Parm map:  -5 -5

so no remaining parameter but op1 is referenced in the predicate?

  parent reply	other threads:[~2023-03-01 13:23 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
2023-03-01 13:23 ` rguenth at gcc dot gnu.org [this message]
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-uuhTcCWVcz@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).