Article View: comp.os.linux.hardware
Article #810Re: P4 vs Athlon for Linux latexing, is gcc-2.95 responsible?
From: David E. Konerding
Date: Mon, 17 Jun 2002 13:05
Date: Mon, 17 Jun 2002 13:05
33 lines
2818 bytes
2818 bytes
In article <x5u1o243mw.fsf@tupik.goethe.zz>, David Kastrup wrote: > fammacd=!SPAM^nothanks@garden.net (George Macdonald) writes: > >> On Sun, 16 Jun 2002 09:30:49 GMT, "Robert Myers" <rmyers1400@attbi.com> >> wrote: >> >> > >> >Without SSE2, which requires that loops be vectorized, a 1.7GHz P2 >> >is a very weak foating point performer, as many have noted, and as >> >you have confirmed for yourself. If I take naive code compiled >> >with icc, my overclocked Celeron running at 1.5MHz will beat a >> >1.7GHz P4 every time. >> >> Are you sure about this? I thought the idea with P4's SSE2 was that >> for scalar calcs you have addressable registers (no stack) and >> therefore no need of the FXCH instructions for stack swaps and it >> runs faster than the old x87 FPU. I've no experience yet but that's >> how I read things. > > The way "how [you] read things" can be improved upon. For an > example, tell us how you read the first two words of the paragraph > you quoted above. You can't just take the first two words of the quoted paragraph, because the sentence itself is factually incorrect: "Without SSE2, which requires that loops be vectorized..." SSE2 can be used as a scalar unit, or as a vector unit. There is some question of whether or not it's a win when used as a scalar unit-- although George does give a suggestion why it could be. Dave
Technical Details
Message-ID:
<slrnagrnke.an3.dakone@master.hanalei>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newshub.sdsu.edu!news-hog.berkeley.edu!ucberkeley!agate.berkeley.edu!agate!not-for-mailReferences:
<3D0B57CB.5060406@nospam.com> <cVYO8.93284$pw3.4355@sccrnsc03> <3d0da9af.198043171@news.garden.net> <x5u1o243mw.fsf@tupik.goethe.zz>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: f65d0,ea3300a83f1f851c X-Google-Attributes: gidf65d0,public X-Google-Thread: 1045b9,ea3300a83f1f851c X-Google-Attributes: gid1045b9,public X-Google-ArrivalTime: 2002-06-17 06:05:19 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newshub.sdsu.edu!news-hog.berkeley.edu!ucberkeley!agate.berkeley.edu!agate!not-for-mail From: "David E. Konerding" <dakone@uclink.berkeley.edu> Newsgroups: comp.os.linux.hardware,gnu.gcc,comp.sys.ibm.pc.hardware.chips,comp.text.tex Subject: Re: P4 vs Athlon for Linux latexing, is gcc-2.95 responsible? Followup-To: comp.os.linux.hardware Date: Mon, 17 Jun 2002 13:05:18 +0000 (UTC) Organization: University of California, Berkeley Lines: 33 Message-ID: <slrnagrnke.an3.dakone@master.hanalei> References: <3D0B57CB.5060406@nospam.com> <cVYO8.93284$pw3.4355@sccrnsc03> <3d0da9af.198043171@news.garden.net> <x5u1o243mw.fsf@tupik.goethe.zz> NNTP-Posting-Host: phylogenomics.berkeley.edu X-Trace: agate.berkeley.edu 1024319118 47187 128.32.213.33 (17 Jun 2002 13:05:18 GMT) X-Complaints-To: usenet@agate.berkeley.edu NNTP-Posting-Date: Mon, 17 Jun 2002 13:05:18 +0000 (UTC) User-Agent: slrn/0.9.7.4 (Linux)