public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 since r9-6999
Date: Thu, 10 Feb 2022 07:47:52 +0000	[thread overview]
Message-ID: <bug-104446-4-VaPfjj9XrR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104446-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This testcase is invalid code of course, so anything can happen.  ICEs are bad
though ;-)

Please add to the comment that you don't want this substitution because it
leads
to ICEs, and mention the PR # in the comment.  But better, figure out *why*
this
ICEs later on: it is perfectly normal for combine to create RTL that is
non-sensical but structurally correct, and it should simply not pass recog.
This patch avoids the problem, and does not fix it.  It would be good to know
what the real problem is.

  parent reply	other threads:[~2022-02-10  7:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 19:40 [Bug c/104446] New: [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 gscfq@t-online.de
2022-02-08 21:37 ` [Bug middle-end/104446] " pinskia at gcc dot gnu.org
2022-02-09  7:32 ` rguenth at gcc dot gnu.org
2022-02-09  9:04 ` [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 since r9-6999 jakub at gcc dot gnu.org
2022-02-09 11:13 ` jakub at gcc dot gnu.org
2022-02-09 11:32 ` jakub at gcc dot gnu.org
2022-02-10  7:47 ` segher at gcc dot gnu.org [this message]
2022-02-11 12:52 ` cvs-commit at gcc dot gnu.org
2022-02-11 12:53 ` [Bug middle-end/104446] [9/10/11 " jakub at gcc dot gnu.org
2022-02-19  8:02 ` cvs-commit at gcc dot gnu.org
2022-02-19  8:08 ` [Bug middle-end/104446] [9/10 " jakub at gcc dot gnu.org
2022-05-10  8:23 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:24 ` cvs-commit at gcc dot gnu.org
2022-05-11  6:36 ` jakub 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-104446-4-VaPfjj9XrR@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).