public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Philippe Lafoucrière" <lafou@wanadoo.fr>
To: David Holm <dholm@gentoo.org>
Cc: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)"
Date: 13 Aug 2003 16:28:53 +0200	[thread overview]
Message-ID: <1060784933.7506.39.camel@biproc> (raw)
In-Reply-To: <20030813162432.7decc94e.dholm@gentoo.org>

On Wed, 2003-08-13 at 16:24, David Holm wrote:
> If they really wanted to test the speed why didn't they use more aggressive compiler flags?
> 
> I think it should be investigated which packages could be compiled by icc since
> intel are now providing it for free for non-commercial use. I did some tests with it and
> whetstone (classic fpu benchmark from the 1970's) doubled in speed compared to gcc on a P4, and
> it was about 75% faster on an Athlon-XP. Now float-point isn't everything but from my experience
> icc generally produces better optimized code than gcc unless the application has been hand-tuned
> (like mplayer).
> I tried installing gentoo with CC=icc once but I had problems with many ebuilds so I dropped
> that idea. At the moment extremely few ebuilds support icc.


Just realized that they are using march=pentium3, whereas celeron is a pentium2 (cf /etc/make.conf !). 
the use of march can really slow down the machine I think...


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-13 14:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 13:38 [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Philippe Lafoucrière
2003-08-13 14:07 ` brett holcomb
2003-08-13 15:03   ` Sven Vermeulen
2003-08-13 16:15     ` Alan
2003-08-13 20:30       ` Chris Gianelloni
2003-08-13 14:08 ` Chris Gianelloni
2003-08-13 14:12   ` Brad Laue
2003-08-13 14:20   ` Philippe Lafoucrière
2003-08-13 14:25     ` Philippe Lafoucrière
2003-08-13 14:32     ` Chris Gianelloni
2003-08-13 16:17       ` Alan
2003-08-13 16:22         ` Patrick Kursawe
2003-08-13 20:35           ` Chris Gianelloni
2003-08-13 20:32         ` Chris Gianelloni
2003-08-14 10:02           ` Paul de Vrieze
2003-08-13 21:15     ` FRLinux
2003-08-13 22:49       ` William Kenworthy
2003-08-14  2:04         ` Brian Jackson
2003-08-14 10:10         ` Paul de Vrieze
2003-08-14 12:30         ` Chris Gianelloni
2003-08-14 16:59           ` William Kenworthy
2003-08-14 17:38             ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentooapproach)" matt c
2003-08-14 19:22         ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" FRLinux
2003-08-14 23:01           ` William Kenworthy
2003-08-13 14:24 ` David Holm
2003-08-13 14:28   ` Philippe Lafoucrière [this message]
2003-08-13 16:16     ` Eric Olinger
2003-08-13 19:00   ` Jon Portnoy
2003-08-13 20:02     ` Mike Frysinger
2003-08-14  1:07       ` [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)' donnie berkholz
2003-08-14  1:13         ` Jon Portnoy
2003-08-14 11:01         ` Chris Gianelloni
2003-08-13 14:34 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Stuart Herbert
2003-08-13 14:34 ` Svyatogor
2003-08-13 17:46 ` Adam Porich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1060784933.7506.39.camel@biproc \
    --to=lafou@wanadoo.fr \
    --cc=dholm@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox