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 middle-end/103314] [12 regression] ICE on valid code at -O1 and above on x86_64-linux-gnu: Segmentation fault since r12-5358 Date: Fri, 19 Nov 2021 12:07:16 +0000 [thread overview] Message-ID: <bug-103314-4-mqaNU0gkDN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103314-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103314 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:ea2954df43d4162af23a20c84f4c5485463977ac commit r12-5400-gea2954df43d4162af23a20c84f4c5485463977ac Author: Andrew Pinski <apinski@marvell.com> Date: Fri Nov 19 01:42:41 2021 +0000 Fix tree-optimization/103314 : Limit folding of (type) X op CST where type is a nop convert to gimple There is some re-association code in fold_binary which conflicts with this optimization due keeping around some "constants" which are not INTEGER_CST (1 << -1) so we end up in an infinite loop because of that. So we need to limit this case to GIMPLE level only. OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions. PR tree-optimization/103314 gcc/ChangeLog: * match.pd ((type) X op CST): Restrict the equal TYPE_PRECISION case to GIMPLE only. gcc/testsuite/ChangeLog: * gcc.c-torture/compile/pr103314-1.c: New test.
next prev parent reply other threads:[~2021-11-19 12:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-18 12:39 [Bug c/103314] New: ICE on valid code at -O1 and above on x86_64-linux-gnu: Segmentation fault zhendong.su at inf dot ethz.ch 2021-11-18 12:40 ` [Bug c/103314] " zhendong.su at inf dot ethz.ch 2021-11-18 12:46 ` [Bug middle-end/103314] [12 regression] " pinskia at gcc dot gnu.org 2021-11-18 12:47 ` [Bug middle-end/103314] [12 regression] ICE on valid code at -O1 and above on x86_64-linux-gnu: Segmentation fault since r12-5358 jakub at gcc dot gnu.org 2021-11-18 12:52 ` jakub at gcc dot gnu.org 2021-11-19 1:19 ` pinskia at gcc dot gnu.org 2021-11-19 1:36 ` pinskia at gcc dot gnu.org 2021-11-19 6:33 ` pinskia at gcc dot gnu.org 2021-11-19 12:07 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-19 12:08 ` pinskia at gcc dot gnu.org 2021-11-30 11:54 ` pinskia 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-103314-4-mqaNU0gkDN@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).