public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhaoweiliew at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95424] Failure to optimize division with numerator of 1 Date: Wed, 05 Jan 2022 03:33:34 +0000 [thread overview] Message-ID: <bug-95424-4-DI9bCrLgSn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95424-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95424 Zhao Wei Liew <zhaoweiliew at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #52098|0 |1 is obsolete| | --- Comment #6 from Zhao Wei Liew <zhaoweiliew at gmail dot com> --- Created attachment 52126 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52126&action=edit Optimize 1 / X for integer X Here's a new patch along with test cases.
next prev parent reply other threads:[~2022-01-05 3:33 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-29 20:21 [Bug tree-optimization/95424] New: " gabravier at gmail dot com 2020-06-02 6:46 ` [Bug tree-optimization/95424] " rguenth at gcc dot gnu.org 2021-08-14 23:59 ` pinskia at gcc dot gnu.org 2021-12-30 7:12 ` zhaoweiliew at gmail dot com 2021-12-31 1:16 ` zhaoweiliew at gmail dot com 2021-12-31 1:17 ` zhaoweiliew at gmail dot com 2021-12-31 1:18 ` zhaoweiliew at gmail dot com 2021-12-31 1:19 ` zhaoweiliew at gmail dot com 2022-01-05 3:33 ` zhaoweiliew at gmail dot com [this message] 2022-01-28 18:37 ` cvs-commit at gcc dot gnu.org 2022-01-28 18:41 ` law at gcc dot gnu.org 2022-01-29 16:56 ` cvs-commit at gcc dot gnu.org 2024-01-20 17:16 ` 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-95424-4-DI9bCrLgSn@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).