public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50092] [4.4/4.5 Regression] internal compiler error: in elimination_costs_in_insn, at reload1.c:3633
Date: Thu, 18 Aug 2011 14:44:00 -0000	[thread overview]
Message-ID: <bug-50092-4-VohbAs31oh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50092-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |4.6.2, 4.7.0
            Summary|[4.4/4.5/4.6/4.7            |[4.4/4.5 Regression]
                   |Regression] internal        |internal compiler error: in
                   |compiler error: in          |elimination_costs_in_insn,
                   |elimination_costs_in_insn,  |at reload1.c:3633
                   |at reload1.c:3633           |

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-08-18 14:39:05 UTC ---
Fixed for 4.6+ so far.


  parent reply	other threads:[~2011-08-18 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 17:19 [Bug c/50092] New: " mario.trangoni at intel dot com
2011-08-16  8:49 ` [Bug target/50092] [4.4/4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-08-18  9:08 ` jakub at gcc dot gnu.org
2011-08-18  9:56 ` jakub at gcc dot gnu.org
2011-08-18 14:29 ` jakub at gcc dot gnu.org
2011-08-18 14:39 ` jakub at gcc dot gnu.org
2011-08-18 14:44 ` jakub at gcc dot gnu.org [this message]
2012-03-13 13:32 ` [Bug target/50092] [4.5 " jakub at gcc dot gnu.org
2012-06-20 13:04 ` rguenth at gcc dot gnu.org
2012-07-02 10:09 ` 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-50092-4-VohbAs31oh@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).