public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* today's CVS version fails to build on i586-pc-linux-gnulibc1
@ 1998-04-15 16:09 Joe Buck
  1998-04-17  3:19 ` Gerald Pfeifer
  0 siblings, 1 reply; 3+ messages in thread
From: Joe Buck @ 1998-04-15 16:09 UTC (permalink / raw)
  To: egcs team

Finally got anonymous CVS going on my home Linux box
(i586-pc-linux-gnulibc1, Red Hat 4.2).

I get an internal compiler error when trying to build today's CVS
version, though.  tinfo.cc fails to build.  The output is

./xgcc -B./ -O2   -DIN_GCC   -DUSE_GNULIBC_1 -W -Wall -O2 -g -O2 \
-I./include  -fPIC -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -fexceptions \
-I. -I../../egcs/gcc -I../../egcs/gcc/config -c ../../egcs/gcc/cp/tinfo.cc
../../egcs/gcc/cp/tinfo.cc: In method `void *
__class_type_info::dcast(const cla
ss type_info &, int, void *, const class type_info * = 0, void * = 0)
const':
../../egcs/gcc/cp/tinfo.cc:80: warning: comparison between signed and unsigned
include/typeinfo: At top level:
include/typeinfo:64: Internal compiler error.
include/typeinfo:64: Please submit a full bug report to `egcs-bugs@cygnus.com'.

cc1plus's stack trace when the error occurs is
#0  0x8071eac in mark_vtable_entries (decl=0x823efe4)
    at ../../../egcs/gcc/cp/decl2.c:2359
#1  0x80721f2 in finish_vtable_vardecl (prev=0x82431b8, vars=0x823efe4)
    at ../../../egcs/gcc/cp/decl2.c:2534
#2  0x8072294 in walk_vtables (typedecl_fn=0, 
    vardecl_fn=0x807218c <finish_vtable_vardecl>)
    at ../../../egcs/gcc/cp/decl2.c:2600
#3  0x8072c90 in finish_file () at ../../../egcs/gcc/cp/decl2.c:3138
#4  0x80817f5 in yyparse () at parse.y:336
....


I did cvs update at Wed Apr 15 12:17:56 PDT 1998.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: today's CVS version fails to build on i586-pc-linux-gnulibc1
  1998-04-15 16:09 today's CVS version fails to build on i586-pc-linux-gnulibc1 Joe Buck
@ 1998-04-17  3:19 ` Gerald Pfeifer
  0 siblings, 0 replies; 3+ messages in thread
From: Gerald Pfeifer @ 1998-04-17  3:19 UTC (permalink / raw)
  To: Joe Buck; +Cc: egcs team

On Wed, 15 Apr 1998, Joe Buck wrote:
> I get an internal compiler error when trying to build today's CVS
> version, though.  tinfo.cc fails to build.  The output is

This (and a some further bugs) seem to have been fixed and I just finished
my first successful bootstrap since a couple of days ago...

> I did cvs update at Wed Apr 15 12:17:56 PDT 1998.

...so now it might be a good time for another `cvs update`. ;-)

Gerald
-- 
Gerald Pfeifer (Jerry)      Vienna University of Technology
pfeifer@dbai.tuwien.ac.at   http://www.dbai.tuwien.ac.at/~pfeifer/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: today's CVS version fails to build on i586-pc-linux-gnulibc1
@ 1998-04-17 16:42 Mike Stump
  0 siblings, 0 replies; 3+ messages in thread
From: Mike Stump @ 1998-04-17 16:42 UTC (permalink / raw)
  To: egcs

> Date: Fri, 17 Apr 1998 12:17:14 +0200 (CEST)
> From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>

> This (and a some further bugs) seem to have been fixed and I just finished
> my first successful bootstrap since a couple of days ago...

I can confirm it works better for a sparc-sun-solaris2.5.1 box as
well, time to grab a new cvs tree everyone.  Ding dong those wicked
bugs are gone.

FAIL: tiomisc.cc compilation 

                === libio Summary ===
 
# of expected passes            37
# of unexpected failures        1
# of expected failures          2

                === libstdc++ Summary ===
 
# of expected passes            30

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~1998-04-17 16:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-04-15 16:09 today's CVS version fails to build on i586-pc-linux-gnulibc1 Joe Buck
1998-04-17  3:19 ` Gerald Pfeifer
1998-04-17 16:42 Mike Stump

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).