public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A tale of computing thud and blunder
Date: Mon, 19 Dec 2011 12:41:32 +0700	[thread overview]
Message-ID: <CAA2qdGW4ySDCWvUr08=JZ2f96f=jZ7OHcrGEe2JjdemCwWmD0A@mail.gmail.com> (raw)
In-Reply-To: <4EEE82A5.2010909@gmail.com>

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

On Dec 19, 2011 7:20 AM, "Dale" <rdalek1967@gmail.com> wrote:
>
> Walter Dnes wrote:
>>
>> It's probably the sum total of the effect of all the flags. I've renamed
the thread, to be more accurate. Here's how things went... * right after
the install (presumably with generic i686 code) the PC could not handle
streaming 1080i video from my HDHomerun TV tuner * I misinterpreted output
from gcc diagnostics, and concluded that "march=-native" left several flags
disabled that shouldn't be * acting on that (mis)information), I emerged
system+world+kernel and found that not only could my system handle 1080i,
it could handle a 1080p Youtube clip without problems, after a lot of
buffering. My 5 megabit ADSL connection was the limiting factor there. It's
supposed to be upgraded to 6 megabits one of these days, for some minor
improvement. * I mistakenly thought that it was the additional flags in
CFLAGS during the emerge system+world that boosted the video. Actually, the
emerge would've done the trick. The lesson from this is that, before doing
any benchmarking or heavy-duty usage, one should emerge system+world, to
replace the generic code from the install CD with fully optimized code.
It's easiest to so right after the initial install, so that there are as
few packages to emerge as possible.
>
>
>
> That is good advice too.  When I do a install, I unpack the tarball and
do the normal things and get my make.conf settings done.  Since there is
very little installed anyway, I do a emerge -ev world.  It usually takes
only a hour or so depending on the speed of the rig.  Thing is, you then
have everything compiled with your settings and not the generic ones the
tarball had.  It also updates anything that needs it too.  Even before
amd64 came along I did it this way.  Lots of people use Intel CPUs but I
use AMD.  I don't know what the person that made the tarball uses but
either way, he has to make it generic so that it will run on ANY CPU.
>
> I wonder if they should mention this in the docs?  It seemed to have made
a difference in your case for sure.  You went from not being able to play a
video to being able to play a HD video.
>

Kind of like what I always do when I switch from -march=nocona to
-march=native. (Usually I use -march=nocona to ensure seamless VM migration
on my XenServer-equipped boxen, but for some VMs, i.e., those requiring me
to wring out every last drop of performance, I go native.)

That said, if you want to experience fully the "GCC Graphite"
optimizations, you'll also want to do emerge -ev ;-)

Rgds,

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

  reply	other threads:[~2011-12-19  5:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 21:07 [gentoo-user] -march=native is *EXTREMELY* conservative Walter Dnes
2011-12-17 21:53 ` Dale
2011-12-17 21:58 ` [gentoo-user] " Nikos Chantziaras
2011-12-18  1:10   ` Walter Dnes
2011-12-18 10:34     ` Walter Dnes
2011-12-18 10:45       ` Nikos Chantziaras
2011-12-18 18:10         ` Andrea Conti
2011-12-19  0:05         ` [gentoo-user] A tale of computing thud and blunder Walter Dnes
2011-12-19  0:17           ` Dale
2011-12-19  5:41             ` Pandu Poluan [this message]
2011-12-19  6:15               ` Dale
2011-12-19  6:49                 ` [gentoo-user] " Nikos Chantziaras
2011-12-19  7:21                   ` Dale
2011-12-19 12:49                   ` walt
2011-12-19  8:14                 ` [gentoo-user] " Pandu Poluan
2011-12-19 16:37                 ` Paul Hartman
2011-12-18  1:15 ` [gentoo-user] -march=native is *EXTREMELY* conservative Paul Hartman

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='CAA2qdGW4ySDCWvUr08=JZ2f96f=jZ7OHcrGEe2JjdemCwWmD0A@mail.gmail.com' \
    --to=pandu@poluan.info \
    --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