From: "Juan Manuel Guerrero" Organization: Darmstadt University of Technology To: djgpp-workers AT delorie DOT com Date: Fri, 21 Sep 2001 23:10:39 +0200 Subject: RE: gcc-3.01 seems unstable In-reply-to: <250B3114DA16D511B82C00E0094005F8023FC195@MSGWAW11> X-mailer: Pegasus Mail for Windows (v2.54DE) Message-ID: <7CCCCED233E@HRZ1.hrz.tu-darmstadt.de> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk 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 > > I'm not sure, perhaps this is bad memory problem but could you check the > following file (I got the gcc-3.01 sources from Andris' site) > gnu\gcc-3.01\gcc\cp\rtti.c, line 848 which looks like (the asterisk should > be read as a char of ASCII code 127) > SET_DECL_ASSEMBLER_NAME (name*decl, > when it should look like > SET_DECL_ASSEMBLER_NAME (name_decl, 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.