public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/111922] [11/12/13/14 Regression] ICE in cp with -O2 -fno-tree-fre
Date: Wed, 22 Nov 2023 16:32:40 +0000	[thread overview]
Message-ID: <bug-111922-4-zr9wDBCX4d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111922-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't know the IPA code enough to know whether different operand_type vs.
param_type (in the !types_compatible_p sense) means just user bug (in that case
returning VARYING is perfectly fine), or if it can happen also on valid code,
where say caller has one type of argument and callee a different and there is
an implicit (or explicit) cast in between the two.  The latter case would be
nice to get handled without giving up.
I mean something like
void
foo (int x)
{
  asm volatile ("" : "+r" (x));
}

void
bar (long x)
{
  foo (x);
}

void
baz (long x)
{
  if (x < -42 || x >= 185)
    return;
  bar (x);
}
kind of thing (but making sure we don't inline and IPA-VRP tries to propagate
something etc.).

  parent reply	other threads:[~2023-11-22 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 16:38 [Bug c/111922] New: GCC: internal compiler error: in decompose, at wide-int.h:1049 141242068 at smail dot nju.edu.cn
2023-10-22 16:39 ` [Bug c/111922] " 141242068 at smail dot nju.edu.cn
2023-10-22 16:41 ` [Bug ipa/111922] [11/12/13/14 Regression] ICE in cp with -O2 -fno-tree-fre pinskia at gcc dot gnu.org
2023-10-23 16:51 ` jamborm at gcc dot gnu.org
2023-11-22 14:27 ` jakub at gcc dot gnu.org
2023-11-22 16:25 ` amacleod at redhat dot com
2023-11-22 16:32 ` jakub at gcc dot gnu.org [this message]
2023-11-22 17:29 ` amacleod at redhat dot com
2023-11-22 17:34 ` jakub at gcc dot gnu.org
2023-11-22 17:42 ` amacleod at redhat dot com
2023-11-29 16:51 ` cvs-commit at gcc dot gnu.org
2023-11-29 16:52 ` amacleod at redhat dot com
2023-11-29 23:22 ` sjames at gcc dot gnu.org
2023-11-30 18:31 ` amacleod at redhat dot com

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-111922-4-zr9wDBCX4d@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).