public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49218] Incorrect optimization of a 'for' loop creates an infinite loop Date: Mon, 30 May 2011 11:18:00 -0000 [thread overview] Message-ID: <bug-49218-4-pMDBRo9Erh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49218-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49218 --- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-30 11:15:25 UTC --- Author: rguenth Date: Mon May 30 11:15:20 2011 New Revision: 174429 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174429 Log: 2011-05-30 Richard Guenther <rguenther@suse.de> PR tree-optimization/49218 * tree-vrp.c (adjust_range_with_scev): Properly check whether overflow occured. * gcc.c-torture/execute/pr49218.c: New testcase. Added: trunk/gcc/testsuite/gcc.c-torture/execute/pr49218.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vrp.c
next prev parent reply other threads:[~2011-05-30 11:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-29 2:14 [Bug tree-optimization/49218] New: " personal@e-maxx.ru 2011-05-29 10:23 ` [Bug tree-optimization/49218] " rguenth at gcc dot gnu.org 2011-05-29 11:47 ` mikpe at it dot uu.se 2011-05-29 16:38 ` rguenth at gcc dot gnu.org 2011-05-29 17:20 ` rguenth at gcc dot gnu.org 2011-05-29 17:43 ` rguenth at gcc dot gnu.org 2011-05-29 17:50 ` rguenth at gcc dot gnu.org 2011-05-30 8:36 ` jakub at gcc dot gnu.org 2011-05-30 9:03 ` mikpe at it dot uu.se 2011-05-30 9:14 ` rguenth at gcc dot gnu.org 2011-05-30 11:18 ` rguenth at gcc dot gnu.org [this message] 2011-05-30 11:19 ` rguenth at gcc dot gnu.org 2011-05-30 11:27 ` rguenth 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-49218-4-pMDBRo9Erh@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).