public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105374] [12 Regression] ICE in fold_convert_loc, at fold-const.cc:2580 during GIMPLE pass: reassoc since r12-7338-g884f77b4222289510e1df9db2889b60c5df6fcda Date: Tue, 26 Apr 2022 07:58:13 +0000 [thread overview] Message-ID: <bug-105374-4-fcX1YvTqcb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105374-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105374 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:d4836ac9acd0c991a4fe1dec9438773a2c4eb5ac commit r12-8263-gd4836ac9acd0c991a4fe1dec9438773a2c4eb5ac Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 26 09:57:34 2022 +0200 reassoc: Don't call fold_convert if !fold_convertible_p [PR105374] As mentioned in the PR, we ICE because maybe_fold_*_comparisons returns an expression with V4SImode type and we try to fold_convert it to V4BImode, which isn't allowed. IMHO no matter whether we change maybe_fold_*_comparisons we should play safe on the reassoc side and punt if we can't convert like we punt for many other reasons. This fixes the testcase on ARM. Testcase not included, not exactly sure where and what directives it should have in gcc.target/arm/ testsuite. Christophe, do you think you could handle that incrementally? 2022-04-26 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/105374 * tree-ssa-reassoc.cc (eliminate_redundant_comparison): Punt if !fold_convertible_p rather than assuming fold_convert must succeed.
next prev parent reply other threads:[~2022-04-26 7:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 12:08 [Bug tree-optimization/105374] New: " acoplan at gcc dot gnu.org 2022-04-25 12:09 ` [Bug tree-optimization/105374] " acoplan at gcc dot gnu.org 2022-04-25 13:43 ` jakub at gcc dot gnu.org 2022-04-25 13:44 ` jakub at gcc dot gnu.org 2022-04-25 13:47 ` jakub at gcc dot gnu.org 2022-04-25 14:27 ` clyon at gcc dot gnu.org 2022-04-25 15:23 ` clyon at gcc dot gnu.org 2022-04-25 16:38 ` marxin at gcc dot gnu.org 2022-04-25 16:39 ` marxin at gcc dot gnu.org 2022-04-26 6:33 ` rguenth at gcc dot gnu.org 2022-04-26 7:58 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-26 7:58 ` jakub at gcc dot gnu.org 2022-04-27 8:20 ` cvs-commit 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-105374-4-fcX1YvTqcb@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: linkBe 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).