Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!noc.near.net!public.x.org!kaleb From: kaleb@x.org (Kaleb KEITHLEY) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: GCC 2.7.2 Date: 12 Dec 95 10:39:04 GMT Organization: X Consortium Lines: 21 Message-ID: <kaleb.818764744@exalt> References: <4afqvb$nfm@jabba.fdn.org> <DJEqA6.D0E@ritz.mordor.com> NNTP-Posting-Host: exalt.x.org X-Newsreader: NN version 6.5.0 #5 ritz@ritz.mordor.com (Chris Mauritz) writes: >I was going to fiddle with the latest GCC, but I figured that the >core group stuck with 2.6.3 for a reason...which begs the question... >Why? :-) I don't speak for anyone but myself, but could it possibly be because they don't have a time machine!?!? Both 2.7.1 and 2.7.2 were released after FreeBSD 2.1R. I don't think you needed to be a rocket scientist to figure this one out. ;-) I know the core team are pretty conservative about moving to a new compiler, and with good reason. gcc-2.7.x generates bad code in the X server which will cause it to SEGV when it runs. Same server, compiled with gcc-2.6.3 does not SEGV. I wouldn't be in such a big hurry to move to gcc-2.7.2 if I were you. -- Kaleb KEITHLEY