I forgot to mention that for gcc I did manually add the -march=i686
compiler option.
Jim Richey wrote:
>
> Yes, I'm aware of that. However, I think "commercial purposes" is more
> than using it to build software that is to be sold. I'm under the
> impression that using it to build and deploy a corporate proxy server
> would be considered a commercial purpose.
>
> I built Squid 2.4.STABLE7 on Slackware 8.1 with kernel 2.4.19. The
> system was a PentiumPro 200Mhz with with 160MB RAM and a SCSI II drive
> with Adaptec 2940 controller. For GCC 2.95.3 squid configured without
> any optimizations. For icc (Intel Compiler for Linux 6.0) I manually
> added the optimization for inlining and specific optimizations for the
> PentiumPro (-O3 -axi -xi -tpp6 -ip). For the same content I saw my cache
> hits go from averaging around 12 to 14 msec with gcc to around 2 to 4
> msec with icc. Pages came up noticably faster with the icc version.
> Obviously this is a very brief and unscientific test, but it certainly
> got my attention. One other thing to note is that the code built with
> icc was quite a bit larger than the code built with gcc.
>
> Steve Snyder wrote:
> >
> > You know that Intel's compiler for Linux is free for non-commercial use,
> > right? Unless you're planning on selling the Squid binaries generated by
> > the compiler, licensing costs shouldn't be an issue.
> >
> > This Squid user would be interested in hearing more of your experiences in
> > using Intel's compiler with Squid.
> >
> > Thanks.
>
> --
>
> Jim Richey
> jrichey@highmark.com
> Highmark, Inc.
> http://www.highmark.com
-- Jim Richey jrichey@highmark.com Highmark, Inc. http://www.highmark.comReceived on Fri Sep 13 2002 - 09:48:06 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:19 MST