1 |
although i am against overly tweaking CFLAGS, someone suggested |
2 |
something that might be more sane to ask for: |
3 |
|
4 |
/etc/portage/packages.cflags |
5 |
|
6 |
an easy way to maintain your cflags you worked so hard for to obtain, |
7 |
you can trade them in the forums or ebay and then append to your file, |
8 |
not much work to implement in my eyes, and all the testing work is done |
9 |
by those who want it |
10 |
|
11 |
this way those of you who want a per package set of CFLAGS get it w/o it |
12 |
being an impossible task for gentoo to implement |
13 |
|
14 |
now you just need to get someone to make this happen or say "no, not |
15 |
even that will happen" |
16 |
|
17 |
if the portage team picks it up, make sure to thank Magnade for the idea |
18 |
|
19 |
Daniel |
20 |
|
21 |
|
22 |
Klavs Klavsen wrote: |
23 |
|
24 |
>Hi guys, |
25 |
> |
26 |
>Just read an interesting article about Xeon vs. Opteron from anandtech - |
27 |
>where they really show how much difference compile optimizations (or not) |
28 |
>does - and how it differs for different programs for different processors. |
29 |
> |
30 |
>http://www.anandtech.com/linux/showdoc.aspx?i=2163&p=1 |
31 |
> |
32 |
>To me this clearly shows, that if Gentoo wants the best performance - we |
33 |
>can't use a "one cflags fits them all" approach. I do know that if a |
34 |
>program breaks, those CFLAGS are pulled out in the individual ebuild, but |
35 |
>this is not due to poor performance. |
36 |
> |
37 |
>IMHO the only way for Gentoo to prove its true potential - is to somehow |
38 |
>build an array of compile options, with CPU's on X, programs on Y and |
39 |
>GCC-version on Z. Getting the numbers for each CPU, will ofcourse require |
40 |
>writing tests, for each program - but IMHO this can be done, if we do it |
41 |
>one at a time. |
42 |
> |
43 |
>I would suggest these tests be included like the gentoo-stats program, as |
44 |
>something the individual Gentooist can choose to run after each compile - |
45 |
>which would give him the optimal performance (and recompile X number of |
46 |
>times to test different flags out) on his CPU/program/GCCversion |
47 |
>combination, and at the same time, send the result to a Gentoo database. |
48 |
> |
49 |
>I know I would definetely have the patience to let it test and test again, |
50 |
>if it meant more performance for me Smile |
51 |
> |
52 |
>The end result should be, that Gentoo automagically selects the optimal |
53 |
>CFLAGS (in performance and stability - perhaps with some optimizations |
54 |
>flagged as "unstable" so people can select "optimize for performance" vs. |
55 |
>"optimize for stability") depending on the X, Y and Z from above. |
56 |
> |
57 |
>I would very much like to be one of the guys that gets the ball rolling, |
58 |
>but as I'm not a Gentoo Dev - We (or just I) need to agree with the Gentoo |
59 |
>Dev's on how this could best be done. |
60 |
> |
61 |
>What do you think? am I crazy? It seems to me that the anandtech tests |
62 |
>shows that it is more than just a 1% or 2% difference, with the right |
63 |
>CFLAGS - and that the right CFLAGS for one program, can be the worst for |
64 |
>another on same CPU/GCC combination. |
65 |
> |
66 |
> |
67 |
> |
68 |
> |
69 |
|
70 |
-- |
71 |
gentoo-dev@g.o mailing list |