public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: mmitchel@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/6445: ICE bootstrapping objc for i386-rtems
Date: Fri, 26 Apr 2002 17:26:00 -0000	[thread overview]
Message-ID: <20020427002601.22623.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/6445; it has been noted by GNATS.

From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: mmitchel@gcc.gnu.org, corsepiu@faw.uni-ulm.de,
 	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/6445: ICE bootstrapping objc for i386-rtems
Date: Fri, 26 Apr 2002 19:13:56 -0500

 Mark,
 
 I have done a gcc_update on my 3.1 CVS tree and 
 seem to be still getting the same failure.  Are 
 you sure?  I will rebuild from scratch once
 more just to check.  But a few minutes ago,
 I updated after your post and still got this:
 
 /usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/b-i386-rtems/gcc/xgcc
 -B/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/b-i386-rtems/gcc/ -nostdinc
 -B/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/b-i386-rtems/i386-rtems/newlib/
 -isystem
 /usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/b-i386-rtems/i386-rtems/newlib/targ-include
 -isystem
 /usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/newlib/libc/include
 -B/opt/rtems/i386-rtems/bin/ -B/opt/rtems/i386-rtems/lib/ -isystem
 /opt/rtems/i386-rtems/include -c -I.
 -I/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc -g -O2
 -msoft-float -DHAVE_GTHR_DEFAULT -DIN_GCC -DIN_TARGET_LIBS
 -I/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/objc
 -I/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/../gcc
 -I/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/../gcc/config
 -I../../../gcc
 -I/usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/../include
 /usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/sendmsg.c
 -o sendmsg.o
 /usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/sendmsg.c:
 In function `objc_msg_sendv':
 /usr3/ftp_archive/gnu/gcc/ss/b3.1-branch/gcc-to-merge/libobjc/sendmsg.c:220:
 Internal compiler error in emit_swap_insn, at reg-stack.c:990
 Please submit a full bug report,
 with preprocessed source if appropriate.
 
 
 mmitchel@gcc.gnu.org wrote:
 > 
 > Synopsis: ICE bootstrapping objc for i386-rtems
 > 
 > State-Changed-From-To: analyzed->closed
 > State-Changed-By: mmitchel
 > State-Changed-When: Fri Apr 26 15:39:27 2002
 > State-Changed-Why:
 >     Fixed in GCC 3.1.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6445
 
 -- 
 Joel Sherrill, Ph.D.             Director of Research & Development
 joel@OARcorp.com                 On-Line Applications Research
 Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985


             reply	other threads:[~2002-04-27  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 17:26 Joel Sherrill [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-27 12:36 Joel Sherrill
2002-04-26 17:36 Mark Mitchell
2002-04-26 15:39 mmitchel
2002-04-25 10:33 mmitchel
2002-04-25  6:22 joel
2002-04-25  0:36 corsepiu

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=20020427002601.22623.qmail@sources.redhat.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mmitchel@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).