public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/27795] [4.1 Regression] optimizer produces faulty code [tree-vrp] Date: Tue, 30 May 2006 13:46:00 -0000 [thread overview] Message-ID: <20060530134531.15563.qmail@sourceware.org> (raw) In-Reply-To: <bug-27795-12751@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2006-05-30 13:45 ------- We transform the loop into an infinite loop. Looks like a sort-of-dup of PR27639 and/or PR26719. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rakdver at gcc dot gnu dot | |org BugsThisDependsOn| |26719, 27639 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27795
next prev parent reply other threads:[~2006-05-30 13:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-29 16:52 [Bug c++/27795] New: optimizer produces faulty code S dot Diederich at gmx dot de 2006-05-29 16:53 ` [Bug c++/27795] " S dot Diederich at gmx dot de 2006-05-29 16:54 ` S dot Diederich at gmx dot de 2006-05-29 16:58 ` [Bug tree-optimization/27795] [4.1/4.2 Regression] optimizer produces faulty code [tree-vrp] pinskia at gcc dot gnu dot org 2006-05-29 17:05 ` [Bug tree-optimization/27795] [4.1 " pinskia at gcc dot gnu dot org 2006-05-29 18:03 ` pinskia at gcc dot gnu dot org 2006-05-30 13:46 ` rguenth at gcc dot gnu dot org [this message] 2006-07-21 12:27 ` rguenth at gcc dot gnu dot org 2006-07-24 8:26 ` rguenth at gcc dot gnu dot org 2006-07-24 8:29 ` 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=20060530134531.15563.qmail@sourceware.org \ --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).