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/103813] [11/12 Regression] Crash in decompose, at wide-int.h:984 fold-const since r11-5271-g4866b2f5db117f9e Date: Tue, 28 Dec 2021 16:41:55 +0000 [thread overview] Message-ID: <bug-103813-4-S3mwkzgriH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103813-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103813 --- Comment #6 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:9258ac53cfcbe546e8b86a433e59343538743f74 commit r12-6135-g9258ac53cfcbe546e8b86a433e59343538743f74 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Dec 28 17:41:24 2021 +0100 fold-const: Fix up fold_truth_andor_1 shift handling [PR103813] Some time ago I've changed const_binop -> wide_int_binop, so that it punts on shifts by negative count. fold_truth_andor_1 doesn't check the results of const_binop (?SHIFT_EXPR, ) though and assumes they will be always non-NULL, which is no longer the case. 2021-12-28 Jakub Jelinek <jakub@redhat.com> PR middle-end/103813 * fold-const.c (fold_truth_andor_1): Punt of const_binop LSHIFT_EXPR or RSHIFT_EXPR returns NULL. Formatting fix. * gcc.c-torture/compile/pr103813.c: New test.
next prev parent reply other threads:[~2021-12-28 16:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-22 22:29 [Bug c/103813] New: Crash in decompose, at wide-int.h:984 fold-const k.even-mendoza at imperial dot ac.uk 2021-12-22 22:36 ` [Bug middle-end/103813] " pinskia at gcc dot gnu.org 2021-12-22 22:37 ` [Bug middle-end/103813] [11/12 Regression] " pinskia at gcc dot gnu.org 2021-12-22 22:58 ` pinskia at gcc dot gnu.org 2021-12-23 8:34 ` [Bug middle-end/103813] [11/12 Regression] Crash in decompose, at wide-int.h:984 fold-const since r11-5271-g4866b2f5db117f9e marxin at gcc dot gnu.org 2021-12-27 16:48 ` jakub at gcc dot gnu.org 2021-12-28 16:41 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-28 16:43 ` [Bug middle-end/103813] [11 " jakub at gcc dot gnu.org 2022-01-04 13:20 ` rguenth at gcc dot gnu.org 2022-01-24 9:20 ` cvs-commit at gcc dot gnu.org 2022-01-24 9:30 ` 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-103813-4-S3mwkzgriH@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).