From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manfred Hollstein To: manfred@s-direktnet.de Cc: law@cygnus.com, Manfred.Hollstein@ks.sel.alcatel.de, oliva@dcc.unicamp.br, gcc2@cygnus.com, egcs@cygnus.com Subject: Re: New problems with gcc-2.8.0 based code - NOW FIXED! Date: Sat, 27 Dec 1997 12:13:00 -0000 Message-id: <199712271650.RAA00440@saturn.s-direktnet.de> References: <9712110707.AA07283@lts.sel.alcatel.de> <26361.882821354@hurl.cygnus.com> <199712261411.PAA00654@saturn.s-direktnet.de> X-SW-Source: 1997-12/msg01155.html On Fri, 26 December 1997, 15:11:14, manfred@s-direktnet.de wrote: > There are other problems since the merge with gcc-2.8.0, though. > > Up to egcs-1.0 (incl. egcs-971201) I've been able to built my Linux > kernel with `-O6 -march=pentium -mcpu=pentium -fomit-frame-pointer > -malign-loops=0 -malign-jumps=0 -malign-functions=0' _and_ > `-funroll-all-loops'! > > Newer snapshots and gcc-2.8.0-971213 don't allow me to do that; > `-funroll-all-loops' causes `isapnp' and `clock' to fail with > `segmentation violations'. Omitting `-funroll-all-loops' helps for > the most current 2.1.7x kernels, but 2.0.33 still fails if compiled by > gcc-2.8.0 and egcs-971215! > > Did anybody else see similar symptoms? > > Looks - at least for me - like the loop unrolling stuff (and perhaps > other as well) hasn't really been improved by the merge with gcc-2.8.0 > :-( Just compiled my 2.1.76 kernel once again this time using egcs-971225 to see if the `-funroll-all-loops' still persists. IT'S FIXED! I writing this e-mail on the freshly compiled kernel and didn't had any problems so far. I'll only have to reboot later on to sent this mail out into the world, as ISDN is still broken in the most recent kernels :-( Keep up the good work, cheers 1998 Manfred