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 middle-end/52881] [4.8 Regression] ICE due to null pointer deref in cfgloop.c
Date: Wed, 11 Apr 2012 08:14:00 -0000	[thread overview]
Message-ID: <bug-52881-4-yGQrbjlLWk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52881-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52881

--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-04-11 08:13:45 UTC ---
Author: rguenth
Date: Wed Apr 11 08:13:37 2012
New Revision: 186304

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186304
Log:
2012-04-11  Richard Guenther  <rguenther@suse.de>

    PR rtl-optimization/52881
    * ifcvt.c (find_if_case_2): Avoid speculating loop latches.

    * gcc.dg/torture/pr52881.c: New testcase.
    * gcc.dg/torture/pr52913.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr52881.c
    trunk/gcc/testsuite/gcc.dg/torture/pr52913.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/ifcvt.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-04-11  8:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 19:59 [Bug c/52881] New: ICE due to null pointer deref regehr at cs dot utah.edu
2012-04-05 20:43 ` [Bug middle-end/52881] [4.8 Regression] ICE due to null pointer deref in cfgloop.c pinskia at gcc dot gnu.org
2012-04-09 16:21 ` regehr at cs dot utah.edu
2012-04-10 11:34 ` rguenth at gcc dot gnu.org
2012-04-11  8:14 ` rguenth at gcc dot gnu.org [this message]
2012-04-11  8:18 ` 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-52881-4-yGQrbjlLWk@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: link
Be 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).