public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44569] ICE in simplify_subreg for debug insn with CONCATN
Date: Wed, 03 Nov 2010 22:42:00 -0000	[thread overview]
Message-ID: <bug-44569-4-vbgtIfcR44@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44569-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from uros at gcc dot gnu.org 2010-11-03 22:42:42 UTC ---
Author: uros
Date: Wed Nov  3 22:42:39 2010
New Revision: 166281

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166281
Log:
    Revert:
    2010-10-30  Uros Bizjak  <ubizjak@gmail.com>

    PR middle-end/44569
    * lower-suberg.c (simplify_subreg_concatn): For VOIDmode elements,
    determine the mode of a subreg by GET_MODE_INNER of CONCATN RTX.


Modified:
    branches/gcc-4_5-branch/gcc/ChangeLog
    branches/gcc-4_5-branch/gcc/lower-subreg.c


  parent reply	other threads:[~2010-11-03 22:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44569-4@http.gcc.gnu.org/bugzilla/>
2010-10-29 23:11 ` [Bug middle-end/44569] Debug statements passed to rtx rguenth at gcc dot gnu.org
2010-10-30 12:49 ` ubizjak at gmail dot com
2010-10-30 19:55 ` uros at gcc dot gnu.org
2010-10-30 20:38 ` uros at gcc dot gnu.org
2010-10-30 20:50 ` uros at gcc dot gnu.org
2010-10-30 20:55 ` uros at gcc dot gnu.org
2010-10-30 21:02 ` [Bug middle-end/44569] ICE in simplify_subreg for debug insn with CONCATN ubizjak at gmail dot com
2010-11-03 22:42 ` uros at gcc dot gnu.org [this message]
2010-11-03 22:44 ` uros at gcc dot gnu.org
2010-11-03 22:46 ` uros at gcc dot gnu.org
2010-11-03 22:48 ` ubizjak 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-44569-4-vbgtIfcR44@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).