From: Peter Humphrey <prh@gotadsl.co.uk>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Another package that doesn't like GCC 4
Date: Thu, 23 Nov 2006 16:03:08 +0000 [thread overview]
Message-ID: <200611231603.08344.prh@gotadsl.co.uk> (raw)
In-Reply-To: <200611231358.40124.janjitse@gmail.com>
On Thursday 23 November 2006 12:58, Jan Jitse Venselaar wrote:
> ... have you benchmarked in any way the effect of all these
> optimizations on the programs you run? You basically do -Os and then turn
> almost everything on which differs -O2 from -Os, negating the size
> difference, plus some extra very experimental flags, which might increase
> or decrease performance (sorry, but GCC works that way, extra
> optimizations could actually be pessimizations), and probably break some
> programs.
You may have seen some discussion of compiler optimisations on this list, in
which a set of flags have been offered and some people have played with
them. I thought I'd have a go, and was reporting what I'd found. In light
of what you say, I think I'll just go back to a simple set of flags
(-march=k8 -Os -pipe) and leave it at that. And no, I hadn't noticed any
performance improvement with all those flags - another good reason for
reverting. Better, probably. Thanks for the advice.
--
Rgds
Peter
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-23 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 16:28 [gentoo-amd64] Another package that doesn't like GCC 4 Peter Humphrey
2006-11-22 17:38 ` Hemmann, Volker Armin
2006-11-22 18:39 ` Michael Weyershäuser
2006-11-22 23:22 ` Jack Lloyd
2006-11-23 0:52 ` Michael Weyershäuser
2006-11-23 6:47 ` [gentoo-amd64] " Duncan
2006-11-23 11:39 ` [gentoo-amd64] " Peter Humphrey
2006-11-23 12:58 ` Jan Jitse Venselaar
2006-11-23 16:03 ` Peter Humphrey [this message]
2006-11-23 19:21 ` [gentoo-amd64] " Duncan
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=200611231603.08344.prh@gotadsl.co.uk \
--to=prh@gotadsl.co.uk \
--cc=gentoo-amd64@lists.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