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/19986] [meta-bug] fold missing optimizations (compared to RTL) Date: Sat, 22 Apr 2023 08:06:52 +0000 [thread overview] Message-ID: <bug-19986-4-8VHvgfuDhf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19986-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19986 Bug 19986 depends on bug 25186, which changed state. Bug 25186 Summary: (short)(((int)short_var) <<1) should be folded so that the shift is done in the short type https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25186 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
next prev parent reply other threads:[~2023-04-22 8:06 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19986-4@http.gcc.gnu.org/bugzilla/> 2021-06-27 23:26 ` roger at nextmovesoftware dot com 2023-04-22 8:06 ` roger at nextmovesoftware dot com [this message] [not found] <bug-19986-6528@http.gcc.gnu.org/bugzilla/> 2006-01-02 19:37 ` bonzini at gnu dot org 2005-02-16 4:08 [Bug middle-end/19986] New: " pinskia at gcc dot gnu dot org 2005-02-16 4:10 ` [Bug middle-end/19986] " pinskia at gcc dot gnu dot org 2005-02-16 4:34 ` pinskia at gcc dot gnu dot org 2005-03-04 2:55 ` phython at gcc dot gnu dot org 2005-03-04 6:26 ` pinskia at gcc dot gnu dot org 2005-03-11 5:03 ` phython at gcc dot gnu dot org 2005-03-11 5:04 ` phython at gcc dot gnu dot org 2005-04-18 15:20 ` phython at gcc dot gnu dot org 2005-04-20 17:32 ` pinskia at gcc dot gnu dot org 2005-04-23 21:36 ` rguenth at gcc dot gnu dot org 2005-05-17 16:39 ` law at redhat dot com 2005-06-13 0:27 ` phython at gcc dot gnu dot org 2005-08-09 3:06 ` pinskia at gcc dot gnu dot org 2005-09-01 2:15 ` pinskia at gcc dot gnu dot org 2005-09-01 2:27 ` pinskia at gcc dot gnu dot 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-19986-4-8VHvgfuDhf@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).