public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/42436] VRP should mark non-trapping integer divisions Date: Wed, 12 Jan 2022 16:14:34 +0000 [thread overview] Message-ID: <bug-42436-4-yRhc1xuWTk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-42436-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42436 --- Comment #3 from Andrew Macleod <amacleod at redhat dot com> --- What needs to be done here? anything? Looking at VRP1, there is only a single divide left at that point: countm1.6_54 = _12 / _13; and VRP1 is setting the global range of _13 to: _13: unsigned int [2, 2147483647] So at least from that point on, it is trivial to determine the divide is non-trapping even using the global ranges.
next parent reply other threads:[~2022-01-12 16:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-42436-4@http.gcc.gnu.org/bugzilla/> 2022-01-12 16:14 ` amacleod at redhat dot com [this message] 2022-01-13 7:13 ` rguenth at gcc dot gnu.org 2009-12-19 19:41 [Bug tree-optimization/42436] New: " rguenth at gcc dot gnu dot org 2009-12-19 19:42 ` [Bug tree-optimization/42436] " 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-42436-4-yRhc1xuWTk@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).