Message-ID: <250B3114DA16D511B82C00E0094005F8023FC196@MSGWAW11> From: Wojciech Galazka To: "'djgpp-workers AT delorie DOT com'" Subject: RE: gcc-3.01 seems unstable Date: Sat, 22 Sep 2001 11:32:22 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Reply-To: djgpp-workers AT delorie DOT com > -----Original Message----- > From: Juan Manuel Guerrero [mailto:ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De] > > On Fri, 21 Sep 2001, Wojciech Galazka: > > > Then I tried to compile the gcc-3.01 itself assuming that > if it were to > > crash it will. I got several 'Segmentation violation, > > internal compiler error ...' messages but was going on > ontil I got (this is > > in stage 2) > > ../../gcc/libgcc2.c: In function `__muldi3': > > ../../gcc/libgcc2.c:368: Internal compiler error in > > remove_unnecessary_notes, at emit-rtl.c:2897 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > > > and stopped there > > > > OFYI, I have tried to bootstrap gcc301 some days ago in a DOS > session of Win95 > and it fails in *exactely* the same way at *exactely* the > same line of function __muldi3 > of file libgcc2.c. > This is completey independent of the amount of memory I have > used, *independent* > of the memory modules used and *independent* of the > motherboard used. I have not tried > to investigate this in depth because it has been argumented > that gcc301 is ok and > that all this difficulty is a cyrix cpu peculiarity or a > cyrix / motherboard incompatibility. > > Regards, > Guerrero, Jaun M. > Under W2K, using the same compiler (gcc-3.01) and tools I was able to build the compiler but the process stops at libstdc++-v3, the reason being that the files that should have been copied to d:\djgpp.2\gnu\gcc-3.02\build.djg\i586-pc-msdosdjgpp\libstdc++-v3\include\i5 86-pc-msdosdjgpp\bits were copied to the main directory (that is d:\) instead (the -3.02 prefix is only to distinguish the other directory with a clean copy of gcc-3.01 sources) Perhaps the directory name is too long ? The computer is equipped with Intel Pentium III 650 MHz CPU