1 |
On Sat, Dec 11, 2010 at 14:03, Dirkjan Ochtman <djc@g.o> wrote: |
2 |
|
3 |
> On Sat, Dec 11, 2010 at 20:01, Matt Turner <mattst88@g.o> wrote: |
4 |
> > I agree that this could be better. To me, most of the problems with |
5 |
> > this are due to users not knowing which of these should be set for |
6 |
> > their particular CPU. |
7 |
> > |
8 |
> > Instead of having defaults set by a profile, I'd like to figure out a |
9 |
> > way we can have these flags set by default dependent on the user's |
10 |
> > CPU. This might require some additional logic in portage; I don't |
11 |
> > know. |
12 |
> |
13 |
> Yeah, I think setting the best possible default is important here. |
14 |
> |
15 |
|
16 |
+1 to good defaults. |
17 |
|
18 |
Perhaps something along the lines of: If CPU_FLAGS is empty or not defined, |
19 |
set flags based on the -march and -mtune variables. If CPU_FLAGS is set, |
20 |
respect what has been set there and ignore the other logic for defaults. |
21 |
|
22 |
This would allow the average user, and the users building for multiple |
23 |
machines to continue like nothing changed, and users that want to |
24 |
selectively want to enable processor flags can in an easy way. |
25 |
|
26 |
Best, |
27 |
|
28 |
Ross |
29 |
|
30 |
> |
31 |
> Cheers, |
32 |
> |
33 |
> Dirkjan |
34 |
> |
35 |
> |