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/64083] [5 Regression] ICE: in fix_loop_structure, at loop-init.c:252 compiling Linux Kernel
Date: Thu, 27 Nov 2014 09:57:00 -0000	[thread overview]
Message-ID: <bug-64083-4-QA6OZUh1c2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64083-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64083

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Nov 27 09:57:13 2014
New Revision: 218115

URL: https://gcc.gnu.org/viewcvs?rev=218115&root=gcc&view=rev
Log:
2014-11-27  Richard Biener  <rguenther@suse.de>

    PR tree-optimization/64083
    * tree-ssa-threadupdate.c (thread_through_all_blocks): Do not
    forcibly mark loop for removal the wrong way.

    * gcc.dg/torture/pr64083.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr64083.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-ssa-threadupdate.c


  parent reply	other threads:[~2014-11-27  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 13:01 [Bug c/64083] New: ICE compiling Linux Kernel drivers/isdn/i4l/isdn_net.c sasha.levin at oracle dot com
2014-11-26 13:17 ` [Bug middle-end/64083] [5 Regression] ICE: in fix_loop_structure, at loop-init.c:252 compiling Linux Kernel trippels at gcc dot gnu.org
2014-11-26 13:47 ` rguenth at gcc dot gnu.org
2014-11-26 14:10 ` rguenth at gcc dot gnu.org
2014-11-27  9:57 ` rguenth at gcc dot gnu.org [this message]
2014-11-27  9:57 ` rguenth at gcc dot gnu.org
2015-03-05 14:28 ` yroux 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-64083-4-QA6OZUh1c2@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).