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/103855] Missed optimization: 64bit division used instead of 32bit division Date: Wed, 29 Dec 2021 09:41:12 +0000 [thread overview] Message-ID: <bug-103855-4-CWhGMV6A9I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103855-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103855 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- vect_get_range_info is meant for the vectorizer only, what you want is I think get_min_precision which would need to be exported out of internal-fn.c. In any case, it needs to be called still on the trees (SSA_NAMEs or INTEGER_CSTs etc.) during expansion. expand_expr_divmod already performs a different optimization - if both operands are known to have the most significant bit clear (checked with get_range_pos_neg), then it expands it as both signed and unsigned division or modulo and checks if one of them isn't cheaper.
prev parent reply other threads:[~2021-12-29 9:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-29 3:00 [Bug tree-optimization/103855] New: " zhaoweiliew at gmail dot com 2021-12-29 3:16 ` [Bug tree-optimization/103855] " zhaoweiliew at gmail dot com 2021-12-29 3:34 ` pinskia at gcc dot gnu.org 2021-12-29 3:46 ` pinskia at gcc dot gnu.org 2021-12-29 3:53 ` pinskia at gcc dot gnu.org 2021-12-29 8:21 ` zhaoweiliew at gmail dot com 2021-12-29 8:32 ` zhaoweiliew at gmail dot com 2021-12-29 9:41 ` jakub at gcc dot gnu.org [this message]
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-103855-4-CWhGMV6A9I@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).