public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64454] optimize (x%5)%5 Date: Fri, 01 May 2015 10:21:00 -0000 [thread overview] Message-ID: <bug-64454-4-fYVAsXKA3w@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64454-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64454 --- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> --- VRP could still do better: typedef unsigned short T; T f(T x, T y){ // Avoid narrowing in the front-end int ix=x; int iy=y; T z=ix%iy; int iz=z; return z%iy; } ix and iy both have range [0, 65535], but we don't optimize _9 = _5 & 65535; because Visiting statement: _5 = ix_2 % iy_4; Found new range for _5: VARYING Whereas (since the type is unsigned, the signed case is slightly more complicated but should still be doable) the range for _5 should be the intersection of [0, 65535] (at most max(ix_2)) and [0, 65534] (at most max(iy_4)-1). Even in the constant case, if x has range [0, 3], VRP currently says that x%7 has range [0, 6].
next prev parent reply other threads:[~2015-05-01 10:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-31 12:25 [Bug tree-optimization/64454] New: " glisse at gcc dot gnu.org 2015-01-02 20:35 ` [Bug tree-optimization/64454] " glisse at gcc dot gnu.org 2015-01-12 17:54 ` jakub at gcc dot gnu.org 2015-01-12 19:53 ` glisse at gcc dot gnu.org 2015-01-12 20:45 ` jakub at gcc dot gnu.org 2015-01-12 20:52 ` jakub at gcc dot gnu.org 2015-01-12 21:16 ` jakub at gcc dot gnu.org 2015-05-01 10:21 ` glisse at gcc dot gnu.org [this message] 2015-05-09 15:40 ` glisse at gcc dot gnu.org 2015-05-15 17:40 ` glisse at gcc dot gnu.org 2015-05-15 18:07 ` pinskia at gcc dot gnu.org 2015-05-15 18:30 ` glisse at gcc dot gnu.org 2022-02-24 10:33 ` 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-64454-4-fYVAsXKA3w@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).