public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113105] Missing optimzation: fold `div(v, a) * b + rem(v, a)` to `div(v, a) * (b - a) + v` Date: Thu, 21 Dec 2023 22:51:45 +0000 [thread overview] Message-ID: <bug-113105-4-XvtKOvm2H3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113105-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113105 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- So, e.g. on x86_64, unsigned int f1 (unsigned val) { return val / 10 * 16 + val % 10; } unsigned int f2 (unsigned val) { return val / 10 * 6 + val; } unsigned int f3 (unsigned val, unsigned a, unsigned b) { return val / a * b + val % a; } unsigned int f4 (unsigned val, unsigned a, unsigned b) { return val / a * (b - a) + val % a; } unsigned int f5 (unsigned val) { return val / 93 * 127 + val % 93; } unsigned int f6 (unsigned val) { return val / 93 * (127 - 93) + val; } f2, f3 and f5 are shorter compared to f1, f4 and f6 at -O2. With -Os, f3 is shorter than f4, while f1/f2 and f5/f6 are the same size (and also same number of insns there, perhaps f1 better than f2 as it uses shift rather than imul). So, this is really something that needs to take into account the machine specific expansion etc., isn't a clear winner all the time.
next prev parent reply other threads:[~2023-12-21 22:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-21 8:50 [Bug tree-optimization/113105] New: " xxs_chy at outlook dot com 2023-12-21 16:06 ` [Bug tree-optimization/113105] " pinskia at gcc dot gnu.org 2023-12-21 16:09 ` jakub at gcc dot gnu.org 2023-12-21 17:16 ` xxs_chy at outlook dot com 2023-12-21 17:50 ` jakub at gcc dot gnu.org 2023-12-21 22:51 ` jakub at gcc dot gnu.org [this message] 2023-12-23 10:02 ` xxs_chy at outlook dot com 2024-05-30 4:46 ` 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-113105-4-XvtKOvm2H3@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).