public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45552] [graphite] ICE in sese_loop_depth, at sese.h:172
Date: Tue, 14 Dec 2010 17:18:00 -0000	[thread overview]
Message-ID: <bug-45552-4-RUiUcLYP9C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45552-4@http.gcc.gnu.org/bugzilla/>

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

Sebastian Pop <spop at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2010.12.14 17:17:49
         AssignedTo|unassigned at gcc dot       |spop at gcc dot gnu.org
                   |gnu.org                     |
     Ever Confirmed|0                           |1

--- Comment #2 from Sebastian Pop <spop at gcc dot gnu.org> 2010-12-14 17:17:49 UTC ---
Mine.
I can see this ICE on the 4.5 branch.
On trunk this has been fixed.


       reply	other threads:[~2010-12-14 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45552-4@http.gcc.gnu.org/bugzilla/>
2010-12-14 17:18 ` spop at gcc dot gnu.org [this message]
2010-12-14 17:24 ` spop at gcc dot gnu.org
2010-12-14 19:19 ` spop at gcc dot gnu.org
2010-12-17 22:23 ` spop at gcc dot gnu.org
2010-12-23 18:53 ` spop at gcc dot gnu.org
2010-09-06  4:35 [Bug tree-optimization/45552] New: " tolkiendili at gmail dot com
2010-09-06  4:36 ` [Bug tree-optimization/45552] " tolkiendili at gmail dot com

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-45552-4-RUiUcLYP9C@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).