public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kugan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/52904] -Wstrict-overflow false alarm with bounded loop Date: Fri, 08 Aug 2014 10:21:00 -0000 [thread overview] Message-ID: <bug-52904-4-CfnW4JqWqo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52904-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52904 kugan at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |kugan at gcc dot gnu.org Resolution|--- |WORKSFORME --- Comment #9 from kugan at gcc dot gnu.org --- Incorrect warning is gone from the latest trunk build. VRP is now able to detect the correct range. This bug can now be closed. ---------------------------------------------------- Value ranges after VRP: channel_8: [1, 1023] EQUIVALENCES: { channel_10 } (1 elements) channel_10: [1, 1024] channel_15: [0, 1023] .MEM_16: VARYING Removing basic block 5 wait_reading_process_output () { int channel; int nfds; <bb 2>: <bb 3>: # channel_15 = PHI <channel_10(3), 0(2)> foo (channel_15); channel_10 = channel_15 + 1; if (channel_10 != 1024) goto <bb 3>; else goto <bb 4>; <bb 4>: return 0; }
next prev parent reply other threads:[~2014-08-08 10:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-08 8:59 [Bug c/52904] New: " eggert at gnu dot org 2012-04-08 8:59 ` [Bug c/52904] " eggert at gnu dot org 2012-04-08 9:02 ` eggert at gnu dot org 2012-04-08 10:05 ` [Bug tree-optimization/52904] " pinskia at gcc dot gnu.org 2012-04-10 12:18 ` rguenth at gcc dot gnu.org 2013-12-12 17:12 ` Laurent.Rineau__gcc at normalesup dot org 2013-12-12 18:19 ` Laurent.Rineau__gcc at normalesup dot org 2013-12-12 19:34 ` eggert at gnu dot org 2014-08-08 10:21 ` kugan at gcc dot gnu.org [this message] 2014-08-08 22:16 ` kugan at gcc dot gnu.org 2014-08-18 6:29 ` kugan at gcc dot gnu.org 2021-09-14 7:09 ` 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-52904-4-CfnW4JqWqo@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).