[gentoo-user] mplayer compilation

[gentoo-user] mplayer compilation

[Pawel K]

Hello
I'm compiling gentoo on P4 an use my system HD both on
pentium 4 and pentium 3. My make.conf looks like:

CFLAGS="-march=pentium3"
CHOST="i686-pc-linux-gnu"

It works good for all packages but mplayer. Mplayer is
always compiled for p4 when compiled on p4 and for p3
when it is compiled on p3.

How can I force it to be always compiled for p3?

I don't want to compile it on my p3 since it is to
slow.

Thank You for help.


 
____________________________________________________________________________________
Sponsored Link

Mortgage rates near 39yr lows. 
$310k for $999/mo. Calculate new payment! 
www.LowerMyBills.com/lre
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mplayer compilation

[Bo Ørsted Andresen]

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

On Monday 20 November 2006 15:22, Pawel K wrote:
> I'm compiling gentoo on P4 an use my system HD both on
> pentium 4 and pentium 3. My make.conf looks like:
>
> CFLAGS="-march=pentium3"
> CHOST="i686-pc-linux-gnu"
>
> It works good for all packages but mplayer. Mplayer is
> always compiled for p4 when compiled on p4 and for p3
> when it is compiled on p3.
>
> How can I force it to be always compiled for p3?
>
> I don't want to compile it on my p3 since it is to
> slow.

Well, actually the mplayer ebuild don't care about your CFLAGS unless you 
enable the custom-cflags USE flag. Otherwise march is entirely unset. So any 
binpkg made for mplayer on your p4 should work just fine on your p3 as long 
as you don't enable that USE flag.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] mplayer compilation

[Hans-Werner Hilse]

Hi,

On Mon, 20 Nov 2006 15:52:13 +0100
Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:

> Well, actually the mplayer ebuild don't care about your CFLAGS unless you 
> enable the custom-cflags USE flag. Otherwise march is entirely unset.

No, the mplayer configure script would autodetect optimization and set
the result as -march and -mcpu (and will also enable -O4).

All such checking would of course be runtime only and your statement
about march would be true if the cpudetection USE flag is set.

Don't ask me about what happens when both custom-cflags and
cpudetection are enabled... :-)

-hwh

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mplayer compilation

[Uwe Thiem]

On 20 November 2006 18:18, Hans-Werner Hilse wrote:
> Hi,
>
> On Mon, 20 Nov 2006 15:52:13 +0100
>
> Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
> > Well, actually the mplayer ebuild don't care about your CFLAGS unless you
> > enable the custom-cflags USE flag. Otherwise march is entirely unset.
>
> No, the mplayer configure script would autodetect optimization and set
> the result as -march and -mcpu (and will also enable -O4).
>
> All such checking would of course be runtime only and your statement
> about march would be true if the cpudetection USE flag is set.
>
> Don't ask me about what happens when both custom-cflags and
> cpudetection are enabled... :-)

Well, it matches. ;-)

Uwe

-- 
Mark Twain: I rather decline two drinks than a German adjective.
http://www.SysEx.com.na
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mplayer compilation

[Daniel Iliev]

Hans-Werner Hilse wrote:
> Hi,
>
> On Mon, 20 Nov 2006 15:52:13 +0100
> Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
>
>   
>> Well, actually the mplayer ebuild don't care about your CFLAGS unless you 
>> enable the custom-cflags USE flag. Otherwise march is entirely unset.
>>     
>
> No, the mplayer configure script would autodetect optimization and set
> the result as -march and -mcpu (and will also enable -O4).
>
> All such checking would of course be runtime only and your statement
> about march would be true if the cpudetection USE flag is set.
>
> Don't ask me about what happens when both custom-cflags and
> cpudetection are enabled... :-)
>
> -hwh
>
>   

I don't think there is such an option for gcc "-O4". AFAIK the shorthand
optimization options are -O, -O0, -O1, -O2, -O3 and -Os" At least the
man page reads:


Optimization Options
    -falign-functions=n -falign-jumps=n -falign-labels=n -falign-loops=n
    -fbounds-check -fmudflap -fmudflapth -fmudflapir
    -fbranch-probabilities -fprofile-values -fvpt
    -fbranch-target-load-optimize -fbranch-target-load-optimize2
    -fbtr-bb-exclusive -fcaller-saves -fcprop-registers
    -fcse-follow-jumps -fcse-skip-blocks -fcx-limited-range
    -fdata-sections -fdelayed-branch -fdelete-null-pointer-checks
    -fearly-inlining -fexpensive-optimizations -ffast-math -ffloat-store
    -fforce-addr -ffunction-sections -fgcse -fgcse-lm -fgcse-sm
    -fgcse-las -fgcse-after-reload -floop-optimize -fcrossjumping
    -fif-conversion -fif-conversion2 -finline-functions
    -finline-functions-called-once -finline-limit=n
    -fkeep-inline-functions -fkeep-static-consts -fmerge-constants
    -fmerge-all-constants -fmodulo-sched -fno-branch-count-reg
    -fno-default-inline -fno-defer-pop -floop-optimize2
    -fmove-loop-invariants -fno-function-cse
    -fno-guess-branch-probability -fno-inline -fno-math-errno
    -fno-peephole -fno-peephole2 -funsafe-math-optimizations
    -funsafe-loop-optimizations -ffinite-math-only -fno-trapping-math
    -fno-zero-initialized-in-bss -fomit-frame-pointer
    -foptimize-register-move -foptimize-sibling-calls
    -fprefetch-loop-arrays -fprofile-generate -fprofile-use -fregmove
    -frename-registers -freorder-blocks -freorder-blocks-and-partition
    -freorder-functions -frerun-cse-after-loop -frerun-loop-opt
    -frounding-math -fschedule-insns -fschedule-insns2
    -fno-sched-interblock -fno-sched-spec -fsched-spec-load
    -fsched-spec-load-dangerous -fsched-stalled-insns=n
    -fsched-stalled-insns-dep=n -fsched2-use-superblocks
    -fsched2-use-traces -freschedule-modulo-scheduled-loops
    -fsignaling-nans -fsingle-precision-constant -fstack-protector
    -fstack-protector-all -fstrength-reduce -fstrict-aliasing -ftracer
    -fthread-jumps -funroll-all-loops -funroll-loops -fpeel-loops
    -fsplit-ivs-in-unroller -funswitch-loops
    -fvariable-expansion-in-unroller -ftree-pre -ftree-ccp -ftree-dce
    -ftree-loop-optimize -ftree-loop-linear -ftree-loop-im
    -ftree-loop-ivcanon -fivopts -ftree-dominator-opts -ftree-dse
    -ftree-copyrename -ftree-sink -ftree-ch -ftree-sra -ftree-ter
    -ftree-lrs -ftree-fre -ftree-vectorize -ftree-vect-loop-version
    -ftree-salias -fweb -ftree-copy-prop -ftree-store-ccp
    -ftree-store-copy-prop -fwhole-program --param name=value -O -O0 -O1
    -O2 -O3 -Os 


-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

gcc optimization levels (was: Re: [gentoo-user] mplayer compilation)

[Boyd Stephen Smith Jr.]

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

On Monday 20 November 2006 15:13, Daniel Iliev <danny@ilievnet.com> wrote 
about 'Re: [gentoo-user] mplayer compilation':
> I don't think there is such an option for gcc "-O4". AFAIK the shorthand
> optimization options are -O, -O0, -O1, -O2, -O3 and -Os"

In addition to -Os, -O will accept any non-negative integer as an argument.  
Currently, anything above 3 does nothing extra.  From what I understand, 
there have been undocumented levels up to 6, but they have always been 
considered unstable (which is why they never appeared in documentation).

The quickest way to recognize a Gentoo ricer is someone that 
has -O4, -O6, -O99 or something else equally stupid in their CFLAGS.  -O3 
is defensible, as it is at least *supposed to be* stable; anything higher 
is just stupid.

--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: gcc optimization levels (was: Re: [gentoo-user] mplayer compilation)

[Hans-Werner Hilse]

Hi,

On Mon, 20 Nov 2006 23:42:06 -0600 "Boyd Stephen Smith Jr."
<bss03@volumehost.net> wrote:

> On Monday 20 November 2006 15:13, Daniel Iliev <danny@ilievnet.com>
> wrote about 'Re: [gentoo-user] mplayer compilation':
> > I don't think there is such an option for gcc "-O4". AFAIK the
> > shorthand optimization options are -O, -O0, -O1, -O2, -O3 and -Os"
> 
> In addition to -Os, -O will accept any non-negative integer as an
> argument. Currently, anything above 3 does nothing extra.  From what
> I understand, there have been undocumented levels up to 6, but they
> have always been considered unstable (which is why they never
> appeared in documentation).

Hm, I don't know if they we're considerend unstable, but I think they
were too much of a moving target to actually document them. The -O
parameters are passed to gcc's code modules.

> The quickest way to recognize a Gentoo ricer is someone that 
> has -O4, -O6, -O99 or something else equally stupid in their CFLAGS.
> -O3 is defensible, as it is at least *supposed to be* stable;
> anything higher is just stupid.

OK, I agree that this might be an indication that the person just
c&p'ed a part of a wannabee-howto from the forums...

In this case, however, it's the default setting (at least on my
machine) that mplayer choses when it does its own recognizing of the
best settings (and ignores Gentoo's CFLAGS). And I've yet to see it
break... Myself, I would never care about spending my CPU power beyond
anything than -O2, where -O1 is mostly absolutely sufficient. I've seen
broken compile runs for -Os and -O3, but -O2 is the safe thing.

-hwh
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] mplayer compilation

[Alan McKinnon]

On Monday 20 November 2006 16:22, Pawel K wrote:
> Hello
> I'm compiling gentoo on P4 an use my system HD both on
> pentium 4 and pentium 3. My make.conf looks like:
>
> CFLAGS="-march=pentium3"
> CHOST="i686-pc-linux-gnu"
>
> It works good for all packages but mplayer. Mplayer is
> always compiled for p4 when compiled on p4 and for p3
> when it is compiled on p3.
>
> How can I force it to be always compiled for p3?
>
> I don't want to compile it on my p3 since it is to
> slow.

mplayer comes with the cpudetection USE flag set, so it detects your cpu 
type at run time. Which nicely avoids your entire problem :-)

alan
-- 
gentoo-user@gentoo.org mailing list