| gabriel rosenkoetter on Thu, 26 Sep 2002 16:59:17 -0400 |
|
> > On Thu, Sep 26, 2002 at 12:59:52PM -0400, Time wrote: > > > Which of these apply to the Ultra5? None of them. The Ultra 5 has an UltraSparc, which is a sun4u, which is a sparcv9 processor. gcc earlier than 3.x can't optimize for that specifically. (It can optimize for an instruction set better than v7, though, which is the default.) > On Thu, Sep 26, 2002 at 01:04:25PM -0400, Time wrote: > > Again, nevermind 8) - it was one line down: > > > > "debian-sparc-v9","gcc:-DB_ENDIAN -DTERMIO -O3 -mcpu=v8 -mtune=ultrasparc -fomit-frame-pointer -Wall::-D_REENTRANT:-ldl:BN_LLONG RC4_CHAR DES_UNROLL BF_PTR::::::::::dlfcn:linux-shared:-fPIC", With gcc 3.x you can say -mv9 or -multrasparc (they're synonyms). On Thu, Sep 26, 2002 at 02:30:10PM -0400, Time wrote: > and it does! It decreased login time by about 4s across our 100mbps lan. > It now responds in approximately 0.5s. Thanks Bill!!! 8) Sure, but that's just because you switched to v8 code rather than v7 code. Fwiw, switching to v9 code may not speed anything up, as it'll double the size of (inelegantly allocated--that is, using, for instance, int, rather than specifying int32) memory allocations. (v9's 64-bit, everything earlier's 32-bit.) Now, getting gcc 3.x stable and capable of compiling oh, say, itself is a bit more complicated. (I'm wrangling with it on Solaris at the moment to make lsof build usefully.) -- gabriel rosenkoetter gr@eclipsed.net Attachment:
pgpmBp68Gs9Pr.pgp
|
|