Article View: comp.os.linux.hardware
Article #851Re: P4 vs Athlon for Linux latexing, is gcc-2.95 responsible?
From: Steven G. Kargl
Date: Fri, 21 Jun 2002 20:29
Date: Fri, 21 Jun 2002 20:29
38 lines
2857 bytes
2857 bytes
In article <3D1382E0.6B261C98@moene.indiv.nluug.nl>, Toon Moene <toon@moene.indiv.nluug.nl> writes: > "Eric P. McCoy" wrote: > >> Toon Moene <toon@moene.indiv.nluug.nl> writes: > >> > It was put forward by one of the FreeBSD developers on the front row (I >> > couldn't see who it was, because I was back somewhere in the middle of >> > the audience). >> > I suppose he knew what he was talking about. >> >> He must have been talking about an unreleased version, then. > > Would not surprise me. Linus was addressing things happening in 2.5.x, > so > it could well be about an unreleased version of FreeBSD. > You need to be careful when referring to GCC on FreeBSD. The system compiler on 4.x is 2.9.3(+patches). On FreeBSD-current, which will become 5.0, we have troutmask:kargl[258] uname -r -s FreeBSD 5.0-CURRENT troutmask:kargl[259] gcc -v Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.1 [FreeBSD] 20020509 (prerelease) To muddy the waters, you can install GCC from the ports collection. You have your choices of ports/gcc27, ports/gcc28, ports/gcc295, ports/gcc30 ports/gcc31 and ports/gcc32 -- Steve http://troutmask.apl.washington.edu/~kargl/
Technical Details
Message-ID:
<af02c5$24eu$1@nntp6.u.washington.edu>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.u.washington.edu!140.142.17.34.MISMATCH!news.u.washington.edu!not-for-mailReferences:
<3D0B57CB.5060406@nospam.com> <cVYO8.93284$pw3.4355@sccrnsc03> <3D0C8986.5090104@nospam.com> <3D10EF45.703B0F1@moene.indiv.nluug.nl> <87lm997vl0.fsf@katmai.local> <3D122431.4F2D9002@moene.indiv.nluug.nl> <87hejwmv9j.fsf@katmai.local> <3D1382E0.6B261C98@moene.indiv.nluug.nl>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f9e16,ea3300a83f1f851c
X-Google-Attributes: gidf9e16,public
X-Google-Thread: 102b32,ea3300a83f1f851c
X-Google-Attributes: gid102b32,public
X-Google-Thread: 1094ba,b32aa620bb2987b1
X-Google-Attributes: gid1094ba,public
X-Google-Thread: 1045b9,ea3300a83f1f851c
X-Google-Attributes: gid1045b9,public
X-Google-Thread: f65d0,ea3300a83f1f851c
X-Google-Attributes: gidf65d0,public
X-Google-ArrivalTime: 2002-06-21 13:40:01 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.u.washington.edu!140.142.17.34.MISMATCH!news.u.washington.edu!not-for-mail
From: kargl@troutmask.apl.washington.edu (Steven G. Kargl)
Newsgroups: comp.os.linux.hardware,gnu.gcc,comp.sys.ibm.pc.hardware.chips,comp.text.tex,comp.lang.fortran
Subject: Re: P4 vs Athlon for Linux latexing, is gcc-2.95 responsible?
Date: 21 Jun 2002 20:29:57 GMT
Organization: University of Washington
Lines: 38
Message-ID: <af02c5$24eu$1@nntp6.u.washington.edu>
References: <3D0B57CB.5060406@nospam.com> <cVYO8.93284$pw3.4355@sccrnsc03>
<3D0C8986.5090104@nospam.com> <3D10EF45.703B0F1@moene.indiv.nluug.nl>
<87lm997vl0.fsf@katmai.local> <3D122431.4F2D9002@moene.indiv.nluug.nl>
<87hejwmv9j.fsf@katmai.local>
<3D1382E0.6B261C98@moene.indiv.nluug.nl>
NNTP-Posting-Host: troutmask.apl.washington.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: nntp6.u.washington.edu 1024691397 70110 (None) 140.142.17.38
X-Complaints-To: help@cac.washington.edu
X-Newsreader: knews 1.0b.1