public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Jönsson" <c.christian.joensson@telia.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8183: ICE when compiling classes with virtual base class on sparc64-sun-solaris2.8
Date: Fri, 06 Dec 2002 08:26:00 -0000	[thread overview]
Message-ID: <20021206162602.3487.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8183; it has been noted by GNATS.

From: =?iso-8859-1?Q?Christian_J=F6nsson?= <c.christian.joensson@telia.com>
To: <gcc-gnats@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<rschiele@uni-mannheim.de>,
	<gcc-bugs@gcc.gnu.org>,
	<ghazi@caip.rutgers.edu>,
	<nobody@gcc.gnu.org>
Cc: <aurora-sparc-devel@linuxpower.org>
Subject: Re: c++/8183: ICE when compiling classes with virtual base class on sparc64-sun-solaris2.8
Date: Fri, 6 Dec 2002 17:23:20 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
 gcc&p
 r=3D8183
 
 I would just like to report that there is a problem also on gcc 3.3 =
 20021205
 sparc64-linux:
 
 chj@u1sparc:~$ !858
 /usr/local/src/gcc-binutils/trunk/objdir/gcc/xgcc -shared-libgcc
 -B/usr/local/src/gcc-binutils/trunk/objdir/gcc/ -nostdinc++
 -L/usr/local/src/gcc-binutils/trunk/objdir/sparc64-linux/libstdc++-v3/src=
 
 -L/usr/local/src/gcc-binutils/trunk/objdir/sparc64-linux/libstdc++-v3/src=
 /.l
 ibs -B/usr/local/gcc-binutils/sparc64-linux/bin/
 -B/usr/local/gcc-binutils/sparc64-linux/lib/ -isystem
 /usr/local/gcc-binutils/sparc64-linux/include
 -L/usr/local/src/gcc-binutils/trunk/objdir/ld -nostdinc++
 -I/usr/local/src/gcc-binutils/trunk/objdir/sparc64-linux/libstdc++-v3/inc=
 lud
 e/sparc64-linux
 -I/usr/local/src/gcc-binutils/trunk/objdir/sparc64-linux/libstdc++
 -v3/include
 -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/libstdc++-v3/libsupc++
 -I/usr/local/src/gcc-binutils/trunk/gcc-binutils/libstdc++-v3/libmath -g =
 -O2
 -D_GNU_SOURCE -fno-implicit-templates -Wall -Wno-format -W =
 -Wwrite-strings
 -Winline -fdiagnostics-show-location=3Donce -ffunction-sections
 -fdata-sections -g -c
 ~chj/ice.ii -fPIC -DPIC -o /tmp/out.o
 /home/chj/ice.ii:4: internal compiler error: in lookup_base_r, at
 cp/search.c:  283
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 chj@u1sparc:~$
 
 This was on a Aurora SPARC Linux 0.42 build (Douglas) Ultra1
 sun4u system with these packages:
 
 binutils 2.13.1 20021204 sparc64-linux
 bison-1.35-1
 dejagnu-1.4.3-0   (built
 ftp://ftp.gnu.org/gnu/dejagnu/dejagnu-1.4.3-0.src.rpm)
 expect-5.32.2-67
 gcc 3.2.2 20021122 (prerelease) sparc64-linux
 glibc-2.2.5-40
 glibc64-2.2.5-40
 kernel-2.4.19-1.2sparc
 tcl-8.3.3-67
 
 


             reply	other threads:[~2002-12-06 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  8:26 Christian Jönsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27 15:48 bangerth
2003-01-26 15:16 Christian Jönsson
2003-01-26 12:36 Robert Schiele
2003-01-11  8:46 Christian Jönsson
2003-01-09 13:06 Robert Schiele
2003-01-09 12:16 Christian Jönsson
2002-12-18  9:41 bangerth
2002-10-10  2:06 rschiele

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=20021206162602.3487.qmail@sources.redhat.com \
    --to=c.christian.joensson@telia.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).