public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/48189] [4.7 Regression] ICE: SIGFPE (division by zero) in in predict_loops () at predict.c:991 with --param max-predicted-iterations=0 Date: Fri, 19 Apr 2013 08:20:00 -0000 [thread overview] Message-ID: <bug-48189-4-F4gAn2ebIJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48189-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48189 --- Comment #14 from Marek Polacek <mpolacek at gcc dot gnu.org> 2013-04-19 08:20:11 UTC --- Author: mpolacek Date: Fri Apr 19 08:18:29 2013 New Revision: 198085 URL: http://gcc.gnu.org/viewcvs?rev=198085&root=gcc&view=rev Log: Backport from mainline 2013-01-08 Steven Bosscher <steven@gcc.gnu.org> Jakub Jelinek <jakub@redhat.com> PR tree-optimization/48189 * predict.c (predict_loops): If max is 0, don't call compare_tree_int. If nitercst is 0, don't predict the exit edge. * gcc.dg/pr48189.c: New test. Added: branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/pr48189.c Modified: branches/gcc-4_7-branch/gcc/ChangeLog branches/gcc-4_7-branch/gcc/predict.c branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
prev parent reply other threads:[~2013-04-19 8:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-18 16:24 [Bug tree-optimization/48189] New: [4.3/4.4/4.5/4.6/4.7 " zsojka at seznam dot cz 2011-03-21 12:54 ` [Bug tree-optimization/48189] " rguenth at gcc dot gnu.org 2011-04-10 10:44 ` rguenth at gcc dot gnu.org 2011-04-10 13:33 ` steven at gcc dot gnu.org 2011-06-27 15:15 ` rguenth at gcc dot gnu.org 2011-12-20 13:21 ` [Bug tree-optimization/48189] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org 2012-03-13 15:40 ` [Bug tree-optimization/48189] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org 2012-03-29 14:37 ` hubicka at gcc dot gnu.org 2012-07-02 12:21 ` rguenth at gcc dot gnu.org 2013-01-08 15:03 ` [Bug tree-optimization/48189] [4.6/4.7/4.8 " jakub at gcc dot gnu.org 2013-01-09 9:01 ` jakub at gcc dot gnu.org 2013-01-09 9:04 ` [Bug tree-optimization/48189] [4.6/4.7 " jakub at gcc dot gnu.org 2013-04-04 9:16 ` mpolacek at gcc dot gnu.org 2013-04-04 11:05 ` mpolacek at gcc dot gnu.org 2013-04-12 15:18 ` [Bug tree-optimization/48189] [4.7 " jakub at gcc dot gnu.org 2013-04-19 8:20 ` mpolacek at gcc dot gnu.org 2013-04-19 8:20 ` mpolacek at gcc dot gnu.org [this message]
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-48189-4-F4gAn2ebIJ@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).