public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/28198] [4.2 Regression] ICE building mips-elf cross compiler
Date: Fri, 30 Jun 2006 11:21:00 -0000	[thread overview]
Message-ID: <20060630111856.23661.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28198-9863@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2006-06-30 11:18 -------
(In reply to comment #7)
>> I updated my sources last night and tried building a native x86
> compiler this morning.  I'm getting an internal error still, though
> this one looks different.
> internal compiler error:\ tree check: expected integer_cst, have scope_ref in
> tree_int_cst_sgn, at tree.c:4484

Yes that is a different one.  You would like to file that ICE seperately as the
orginal bug is fixed.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED


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


      parent reply	other threads:[~2006-06-30 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 11:05 [Bug c/28198] New: " fnf at specifixinc dot com
2006-06-29 11:26 ` [Bug c/28198] " fnf at specifixinc dot com
2006-06-29 13:21 ` pinskia at gcc dot gnu dot org
2006-06-29 13:24 ` pinskia at gcc dot gnu dot org
2006-06-29 13:50 ` pinskia at gcc dot gnu dot org
2006-06-29 16:03 ` [Bug middle-end/28198] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-06-29 18:10 ` pinskia at gcc dot gnu dot org
2006-06-30 11:19 ` fnf at specifix dot com
2006-06-30 11:21 ` pinskia at gcc dot gnu dot org [this message]

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=20060630111856.23661.qmail@sourceware.org \
    --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).