public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/25186] (short)(((int)short_var) <<1) should be folded so that the shift is done in the short type Date: Thu, 02 Sep 2021 07:15:38 +0000 [thread overview] Message-ID: <bug-25186-4-lKFaEVigp5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-25186-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25186 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |easyhack Last reconfirmed|2021-08-21 00:00:00 |2021-9-2 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- The optimization is still not done, the shift could be unconditionally made a logical shift but on the smaller type.
next prev parent reply other threads:[~2021-09-02 7:15 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25186-4@http.gcc.gnu.org/bugzilla/> 2021-09-02 2:03 ` gabravier at gmail dot com 2021-09-02 7:15 ` rguenth at gcc dot gnu.org [this message] 2023-04-22 8:06 ` roger at nextmovesoftware dot com 2005-11-30 18:21 [Bug middle-end/25186] New: (short)(((int)short_var) <<1) should be done in short pinskia at gcc dot gnu dot org 2005-12-01 10:53 ` [Bug middle-end/25186] (short)(((int)short_var) <<1) should be folded so that the shift is done in the short type rguenth at gcc dot gnu dot org 2005-12-01 11:01 ` rguenth at gcc dot gnu dot org 2005-12-01 12:28 ` rguenth at gcc dot gnu dot org 2005-12-01 12:46 ` rguenth at gcc dot gnu dot org 2005-12-01 14:17 ` rguenth at gcc dot gnu dot org 2006-04-05 13:49 ` rguenth 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-25186-4-lKFaEVigp5@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).