public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] cflags for atom
Date: Tue, 22 Oct 2013 11:45:35 +1100	[thread overview]
Message-ID: <CAC=wYCHQgRGz4OesY-3Z-99npurEmZRVhGQMe4gUVb1nrg_jGA@mail.gmail.com> (raw)
In-Reply-To: <CAKkyAYYs-2a0tvMw+5tXqGn_auFmO6sLYLAXW3K1NFLGKBFWYQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]

If you havent already, I would first verify that its actually CPU bound,
before changing CFLAGs and recompiling everything. So take a look at top,
vmstat, mpstat etc when you're noticing slowness. If it is truely CPU bound
and you're going to recompile everything, you could consider upgrading to
the ~ version of gcc first, with the assumption that the optimizations
maybe be better. However, my gut feeling is that you wont get much or any
improvement over your current CFLAGs.

The i686 and -Os ideas are interesting. See if you can find any benchmarks.

Also - try diffing the kernel .configs - maybe you missed something
important on the slow system.

[-- Attachment #2: Type: text/html, Size: 738 bytes --]

  reply	other threads:[~2013-10-22  0:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 14:09 [gentoo-user] cflags for atom Silvio Siefke
2013-10-21 14:33 ` thegeezer
2013-10-21 15:08   ` Silvio Siefke
2013-10-21 15:15 ` Frank Steinmetzger
2013-10-21 16:09   ` Silvio Siefke
2013-10-21 16:40     ` Frank Steinmetzger
2013-10-21 16:54       ` housegregory299
2013-10-21 15:20 ` Joseph
2013-10-21 15:40   ` Frank Steinmetzger
2013-10-22  0:31 ` Alecks Gates
2013-10-22  0:45   ` Adam Carter [this message]
2013-10-22  2:20     ` Frank Steinmetzger
2013-10-22 12:40     ` [gentoo-user] " James

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='CAC=wYCHQgRGz4OesY-3Z-99npurEmZRVhGQMe4gUVb1nrg_jGA@mail.gmail.com' \
    --to=adamcarter3@gmail.com \
    --cc=gentoo-user@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