From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FOp4h-0006UC-L2 for garchives@archives.gentoo.org; Thu, 30 Mar 2006 04:48:00 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k2U4lF66020814; Thu, 30 Mar 2006 04:47:15 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.236]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k2U4hDP0006433 for ; Thu, 30 Mar 2006 04:43:13 GMT Received: by wproxy.gmail.com with SMTP id 50so474314wri for ; Wed, 29 Mar 2006 20:43:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LPVFJ3Id1rVqzGEcTAR562glgaer06oAmxaoU6d+SomT7liFWEgNmWeXYsKNRtoPp403XWzp5027P9ErDSw4sMGE4/3aFwHgQlc7X9DrWwyw4Eqn28Dp3ipenY1WA91fw/i2OmtNfSNSp972I6gQelI3M5F69nvRicc8L+82txk= Received: by 10.54.69.4 with SMTP id r4mr1879760wra; Wed, 29 Mar 2006 20:43:12 -0800 (PST) Received: by 10.54.126.6 with HTTP; Wed, 29 Mar 2006 20:43:12 -0800 (PST) Message-ID: <7573e9640603292043j2fa0f51cxd9bb1f9a75f32ea9@mail.gmail.com> Date: Wed, 29 Mar 2006 21:43:12 -0700 From: "Richard Fish" Sender: richard.j.fish@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [OT] Re: [gentoo-user] Intel Core Duo Processor - Anyone? In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <1143616641.29453.15.camel@neuromancer.home.net> <7573e9640603282355t7ab5a526tfd619e0c9c45a03@mail.gmail.com> <1143646905.21205.31.camel@neuromancer.home.net> <7573e9640603290845h3bedb131m209cc6323aee5848@mail.gmail.com> <442B0C32.3090609@gmail.com> <7573e9640603291634v2f22f489t4ca3448c3e683b09@mail.gmail.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k2U4hDP0006433 X-Archives-Salt: b4722e6c-17b3-4743-b6f6-2baadf98520c X-Archives-Hash: 288d180d44bcb4dac86035c607025cf3 On 3/29/06, Lord Sauron wrote: > www.alienware.com I beg to differ. I could have sworn I saw a laptop > with more than 2G... where was it... wow! You appear to be right! > Darn.. I could have SWORN I saw something with > 2G... Actually, you are right. I neglected the monstrous Clevo laptop. Its an AMD X2 with capacity for 2 optical drives plus 2 hard drives, up to 3G of memory, and a 200W power adapter. Weighs 12-15 lbs, _not_ counting the power adapter! This is acutally a Clevo design, sold by Sager, AGearnotebooks, and many others. Alienware got it with a customized case. All of the reviews I read on it basically said "incredible performance, excellent display, but heavy, noisy, and really hard to describe how large it really is". I was actually considering purchasing this beast...but the noise factor scared me off. Not really appropriate for a shared office or conference room. > compiler helps with the 64-bit part. It gets a bit technical, but > there is a big difference between something made from the ground up as > 64-bit versus something that was made 32-bit and just recompiled > 64-bit. For most applications, this is not true. The vast majority of C/C++ code that runs on a desktop system couldn't care less whether longs and pointers are 32-bits or 64-bits in size. It is a compiler function to deal with that. And it is also a compiler function to determine whether 64-bit or 32-bit registers should be used for a particular operation. FYI, gcc has supported non-x86 64-bit CPUs for a long time, so gcc's 64-bit support is probably more mature than you think. So are the applications...many open source applications were ported and adapted (if necessary) to 64-bit sparc and alpha processors back in the late 90s. There are opportunities for some programs to take advantage of special processor operations through assembly instructions. This is very similar to how 3Dnow, MMX, SSE, et. al. make programs faster. So there may be some specific optimizations for some operations that can be improved over time. An example of an application domain that could benefit from 64-bit is encryption, because for key setups you need to calculate very large numbers. Such numbers could be calculated about twice as fast with 64-bit operations vs 32-bit. *BUT*, this does almost nothing for the actual data encryption itself. A good resource on the 64-bit vs 32-bit issues is to look at AMDs optimization guide for software developers. Chapter 3 is particularly relevant: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25112.PDF -Richard -- gentoo-user@gentoo.org mailing list