public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/102029] [12 Regression] ice: error: type mismatch in ‘lshift_expr’ Date: Mon, 23 Aug 2021 21:52:30 +0000 [thread overview] Message-ID: <bug-102029-4-QOTMXROWEk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102029-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102029 Roger Sayle <roger at nextmovesoftware dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at nextmovesoftware dot com Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |roger at nextmovesoftware dot com --- Comment #3 from Roger Sayle <roger at nextmovesoftware dot com> --- Here's the fix that I'm currently testing... (simplify (convert (lshift:s@0 (convert:s@1 @2) INTEGER_CST@3)) - (if (tree_nop_conversion_p (type, TREE_TYPE (@0)) + (if (INTEGRAL_TYPE_P (type) + && !POINTER_TYPE_P (type) + && tree_nop_conversion_p (type, TREE_TYPE (@0)) && INTEGRAL_TYPE_P (TREE_TYPE (@2)) && TYPE_PRECISION (TREE_TYPE (@2)) <= TYPE_PRECISION (type)) (lshift (convert @2) @3)))
next prev parent reply other threads:[~2021-08-23 21:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-23 19:47 [Bug c/102029] New: " dcb314 at hotmail dot com 2021-08-23 19:50 ` [Bug middle-end/102029] [12 Regression] " pinskia at gcc dot gnu.org 2021-08-23 19:51 ` pinskia at gcc dot gnu.org 2021-08-23 20:21 ` jakub at gcc dot gnu.org 2021-08-23 21:52 ` roger at nextmovesoftware dot com [this message] 2021-08-24 2:00 ` cvs-commit at gcc dot gnu.org 2021-08-24 7:14 ` rguenth at gcc dot gnu.org 2021-08-24 12:23 ` dje at gcc dot gnu.org 2021-08-26 17:52 ` 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-102029-4-QOTMXROWEk@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).